This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Add tests that backtrace and backtrace_symbols produce correct results
"Joseph S. Myers" <joseph@codesourcery.com> writes:
> I'd expect there to be unwind information for read as it's a cancellation
> point; the tests themselves are explicitly built with unwind information.
This is not a multithreaded program, and read is invisible because it
does not create a frame in that case.
$ cat debug/tst-backtrace5.out
Obtained backtrace with 7 functions
Function 0: /home/andreas/src/libc/ppc/debug/tst-backtrace5(handle_signal+0x2c) [0x1000130c]
Function 1: linux-vdso32.so.1(__kernel_sigtramp32+0) [0x100394]
Function 2: /home/andreas/src/libc/ppc/debug/tst-backtrace5(fn+0x90) [0x100017c0]
Function 3: /home/andreas/src/libc/ppc/debug/tst-backtrace5(fn+0x20) [0x10001750]
Function 4: /home/andreas/src/libc/ppc/debug/tst-backtrace5(fn+0x20) [0x10001750]
Function 5: /home/andreas/src/libc/ppc/debug/tst-backtrace5() [0x10001834]
Function 6: /home/andreas/src/libc/ppc/debug/tst-backtrace5(main+0x370) [0x10001170]
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."