On Tue, 29 Sep 2015 09:48:30 -0400 Wayne Sallee <[email protected]> wrote:
> <error: No registers.> Wayne, Tis a stubborn one. Sigh. Can you get a backtrace at all under gdb after the error?; (gdb) bt OK, let's try this alternate approach: gdb g++ (gdb) run -c foo.cc . . > 0x7ffff673e51f ??? (gdb) disassemble 0x7ffff673e51f,+32 (using the actual 0x value gdb gave you instead of the value I used here, 32 bytes here should be much more than enough to see the offending instruction). If still no go (e.g., no stack or some such gdb failure), let's tell g++ to produce a core file on error (-dH): g++ -dH -c foo.cc You should have a core file now in the current directory. If still no core file, try to increase the core size limit and try again (need to be root to do this): ulimit -c unlimited If still no core file is produced, look at what cat /proc/sys/kernel/core_pattern is set to. If core_pattern is not set to "core" then set that: echo "core" > /proc/sys/kernel/core_pattern to tell the kernel to create a core file in whatever the current dir is (have to be root or sudo to do this echo to /proc). and then try g++ again: g++ -dH -c foo.cc After you get a core file, run gdb to look at the core file using the g++ executable to resolve the symbols: gdb -c core g++ and see if backtrace works now: (gdb) bt Cheers, Mike -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
