Re: addr2line reports wrong line number for abort(), gdb reports correctly

2006-08-08 Thread Nick Clifton
Hi Sam, gdb reports: (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb7e989a1 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e9a2b9 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0x0804836b in level_aa () at ab.c:5 #4 0x0804838c in main () at ab.c:10 % addr2line -e ab 0x08048

addr2line reports wrong line number for abort(), gdb reports correctly

2006-07-17 Thread Sam Roberts
I'm trying to use the addr2line source as an example of using bfd to map the addresses from the glibc backtrace() back to file and line number. In the process I realized that addr2line doesn't report the correct address. This seems like a bug. gdb reports: (gdb) bt #0 0xe410 in __kernel_vsy