4 ms·
> - debugging a super large program ? loading gdb may take two minutes while recompiling to add a printf only 3-4 seconds. Relinking a super large program may
by MaulingMonkey 6y ago
> - debugging a super large program ? loading gdb may take two minutes while recompiling to add a printf only 3-4 seconds.
Relinking a super large program may take minutes, whereas loading gdb can get me a backtrace in 3-4 seconds! VS natvis files and other visualizers can hot-reload while I'm looking at a crash dump from production that took hours to trigger/gather/repro!
There are cases for logs - where sufficiently efficient conditional breakpoints are particularly painful to setup, for example - but the only time I've waited minutes for a debugger to respond has been with VS after major system updates as it refreshes a universe of symbols from the symbol server.
Do you have some really slow python scripts auto-loading in GDB or something?
- jcelerier 6y ago> Relinking a super large program may take minutes, whereas loading gdb can get me a backtrace in 3-4 seconds! well, we have definitely opposite experiences :) the main software I work on creates a ~1gb binary in debug mode and lld links that in a few seconds. Bud gdb and lldb, even with gdb-index, and all the optimizations I could find, both make startup slow enough that I can go for a coffee and it's not always finished loading when I'm back