# C++ debugging SlicerCAT takes about 10 minutes to start on Ubuntu

**URL:** <https://discourse.slicer.org/t/c-debugging-slicercat-takes-about-10-minutes-to-start-on-ubuntu/21130>\
**Category:** Development\
**Created:** [December 18, 2021, 6:18pm UTC](https://discourse.slicer.org/t/c-debugging-slicercat-takes-about-10-minutes-to-start-on-ubuntu/21130 "2021-12-18T18:18:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![keri](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/keri/32/11618_2.png) [@keri](https://discourse.slicer.org/u/keri)\
**Post date:** [December 18, 2021, 6:18pm UTC](https://discourse.slicer.org/t/c-debugging-slicercat-takes-about-10-minutes-to-start-on-ubuntu/21130/1 "2021-12-18T18:18:16Z")

</div>

Hi,

Is it ok that SicerCAT takes about 10 minutes to start debugging using C++?

I use QtCreator 4.15.1 on Ubuntu 20.04, gcc 9.3, debugger `usr/bin/gdb`  
PC has 4 physical and 4 logical cores  
The processor: Intel(R) Core™ i7-7700K CPU @ 4.20GHz  
RAM: 20 Gb

The executable is `SlicerCAT/d/Slicer-build/bin/SlicerCATApp-real`

I’ve tried debugging using both startup application and using attach to process.

I’m asking because previously I used to work on Windows 10 and Visual Studio 2019 with laptop about two times less powerful and it used to take maybe 4 minutes to start. That is why I have some doubts and this somehow restricts me in C++ debugging, I have to use std::cout or vtkError/qCritical staff to detect bugs.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 19, 2021, 2:52pm UTC](https://discourse.slicer.org/t/c-debugging-slicercat-takes-about-10-minutes-to-start-on-ubuntu/21130/2 "2021-12-19T14:52:34Z")

</div>

Starting under a debugger should be about as fast as without a debugger, except if you load debug symbols. In Visual Studio by default all available debug symbols are loaded, which takes maybe a minute and if you use VS2022 then I noticed that first time stopping at a breakpoint may take again a minute or so. However, you can reduce this symbol loading time by specifying what symbols to load.