I would assume that configuring with debug would set the O0 flag and that one of the main reasons to do so would be to step through code. Otherwise, why use gdb? Application logs can get you a general sense of what is going on without such a fine level of detail but again, if you are not stepping through code, I dont know what the point of using a code debugger would be.
Thanks, ~Ben On Tue, Aug 13, 2019, 8:45 AM Kornel Benko <[email protected]> wrote: > Am Dienstag, 13. August 2019, 13:20:52 CEST schrieb Pavel Sanda: > > On Mon, Aug 12, 2019 at 06:10:19PM -0400, Benedict Holland wrote: > > > You probably need to compile lyx though. I assume that Lyx uses the O2 > flag > > > for production builds so while error messages and logs are a huge help > > > (minimum working example is the best), unless you can compile with the > O0 > > > flag for gcc, gdb will just return a mess. > > > > For reporting backtrace ('bt' command in gdb) to give us clue where the > crash > > occurred the most important is to compile lyx with debug info included > > (./configure --enable-debug). Otherwise you loose info about line > numbers. > > Even slightly better is to use the command > bt full > this way also the values of some parameters are visible. > > > Unless you want to actively step through the code and watch variables > > 02 vs O0 is less important... > > > > Pavel > > Kornel > >
