https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #4 from Mark Millard <mar...@dsl-only.net> ---
A not as libkvm tied note about which gdb
works better for 32-bit powerpc in at
least some contexts:
I took an a.out (from clang++
targeting powerpc) and tried
/usr/local/bin/gdb and /usr/libexec/gdb
on a core it generated:
# gdb a.out /var/crash/a.out.29973.core
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
. . .
Core was generated by `./a.out'.
Program terminated with signal SIGSEGV, Segmentation fault.
Segmentation fault (core dumped)
(gdb itself Segmentation faulted.)
# /usr/libexec/gdb a.out /var/crash/a.out.29973.core
GNU gdb 6.1.1 [FreeBSD]
. . .
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libc++.so.1...Reading symbols from
/usr/lib/debug//usr/lib/libc++.so.1.debug...done.
. . .
Loaded symbols for /libexec/ld-elf.so.1
#0 0x41b355d0 in _Unwind_SetGR (context=<value optimized out>, index=<value
optimized out>, val=1105281072) at unwind-dw2-fde.h:162
162 {
(gdb) bt
#0 0x41b355d0 in _Unwind_SetGR (context=<value optimized out>, index=<value
optimized out>, val=1105281072) at unwind-dw2-fde.h:162
#1 0x4192e370 in __gxx_personality_v0 (version=<value optimized out>,
actions=<value optimized out>, exceptionObject=0x41e14030, context=0xffffd5c0)
at /usr/src/contrib/libcxxrt/exception.cc:1203
#2 0x41b36234 in _Unwind_RaiseException_Phase2 (exc=<value optimized out>,
context=<value optimized out>) at unwind.inc:66
#3 0x41b35e10 in _Unwind_RaiseException (exc=0xffffd5c0) at unwind.inc:135
#4 0x4192d870 in __cxa_throw (thrown_exception=<value optimized out>,
tinfo=<value optimized out>, dest=<value optimized out>) at
/usr/src/contrib/libcxxrt/exception.cc:774
#5 0x01800954 in main () at exception_test.cpp:5
Current language: auto; currently minimal
The same thing happens for running the a.out inside gdb:
/usr/local/bin/gdb gets a Segmentation fault of its own
and /usr/libexec/gdb works, including allowing the bt.
Historically I've primarily used the system gdb to do my
analysis of clang's code generation problems for targeting
powerpc. Including when I looked at gcc 4.2.1 generated
code for comparison. The above sort of thing is an example
of why.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
