FWIW, it looks like the backtrace is within the C++ start-up code that runs all non-empty constructors for global C++ variables, which gets called before "main" starts for a C++ program. Does (gdb) break call_init before (gdb) run give you a working breakpoint?
It does, but it doesn't seem to be terribly useful in debugging, as it keeps hitting that breakpoint over and over and over.
(gdb) set stop-on-solib-events 1 (gdb) run <<args...>> Stopped due to shared library event (gdb) info shared From To Syms Read Shared Object Library 0x00dc2830 0x00ddb27f Yes /lib/ld-linux.so.2 0x00ae4410 0x00ae45e8 Yes a.out (gdb) c Continuing. Stopped due to shared library event (gdb) info shared From To Syms Read Shared Object Library 0x00dc2830 0x00ddb27f Yes /lib/ld-linux.so.2 0x00ae4410 0x00ae45e8 Yes a.out 0x00e5a840 0x00f68c78 Yes /lib/libc.so.6 etc. You might run afoul of this years-old bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179072 Post the build, or a pointer to it, plus the needed environment? -- -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
