Bug#423631: segfaulting gdb on ia64
* Daniel Jacobowitz [EMAIL PROTECTED] [2007-05-22 10:21]: /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. IIRC there's a configure option you have to specify to use libunwind; maybe that's what's broken. Has there been any progress on this bug? I'd need to use gdb on ia64. :/ -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423631: segfaulting gdb on ia64
On Tue, Jun 05, 2007 at 04:46:56PM +0200, Martin Michlmayr wrote: * Daniel Jacobowitz [EMAIL PROTECTED] [2007-05-22 10:21]: /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. IIRC there's a configure option you have to specify to use libunwind; maybe that's what's broken. Has there been any progress on this bug? I'd need to use gdb on ia64. :/ I have to confess that once I built gdb from CVS, I got distracted with other things. The fate of the debugger, I guess ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423631: segfaulting gdb on ia64
I hit the same problem as the buildd and Kurt. Since I need something more recent than gdb 6.5 in order to handle current ia64 executables, I tried to run it anyway. It's not pretty: $ ./objdir/gdb/gdb gs GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as ia64-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (gdb) set args /home/willy/gnupg/keyanalyze-200204-willy/bsdcan2007/output/graph.ps (gdb) run Starting program: /usr/bin/gs /home/willy/gnupg/keyanalyze-200204-willy/bsdcan2007/output/graph.ps (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x20580e61 in strncat () from /lib/libc.so.6.1 (gdb) bt #0 0x20580e61 in strncat () from /lib/libc.so.6.1 #1 0x4010a8a0 in ?? () /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted I really don't know how to go about debugging the debugger when the previous version of the debugger no longer works. $ gdb ./objdir/gdb/gdb GNU gdb 6.5-debian This GDB was configured as ia64-linux-gnu...BFD: /home/willy/debian/gdb/gdb-6.6.dfsg/objdir/gdb/gdb: don't know how to handle OS specific section `.gnu.hash' [0x6ff6] /home/willy/debian/gdb/gdb-6.6.dfsg/objdir/gdb/gdb: not in executable format: File format not recognized -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423631: segfaulting gdb on ia64
On Tue, May 22, 2007 at 06:00:20AM -0600, Matthew Wilcox wrote: I hit the same problem as the buildd and Kurt. Since I need something more recent than gdb 6.5 in order to handle current ia64 executables, I tried to run it anyway. It's not pretty: If you have some time to look at this, could you try building a CVS checkout of GDB on ia64? Maybe that will work better. /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. That's very strange... -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423631: segfaulting gdb on ia64
On Tue, May 22, 2007 at 08:23:34AM -0400, Daniel Jacobowitz wrote: On Tue, May 22, 2007 at 06:00:20AM -0600, Matthew Wilcox wrote: I hit the same problem as the buildd and Kurt. Since I need something more recent than gdb 6.5 in order to handle current ia64 executables, I tried to run it anyway. It's not pretty: If you have some time to look at this, could you try building a CVS checkout of GDB on ia64? Maybe that will work better. Much better: === gdb Summary === # of expected passes11320 # of unexpected failures69 # of unexpected successes 2 # of expected failures 41 # of known failures 45 # of unresolved testcases 1 # of untested testcases 5 # of unsupported tests 13 (ulimit -c was set to 0, so some of those fails are my fault). Running it against gs, my previous testcase, I now get: Program received signal SIGSEGV, Segmentation fault. 0x20580e61 in strncat () from /lib/libc.so.6.1 (gdb) bt #0 0x20580e61 in strncat () from /lib/libc.so.6.1 #1 0x4010a8a0 in ?? () #2 0x40005970 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) which is a damn sight better than the assertion failure. /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. That's very strange... -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423631: segfaulting gdb on ia64
On Tue, May 22, 2007 at 08:12:07AM -0600, Matthew Wilcox wrote: Much better: Interesting. I don't suppose you want to look into this? /home/willy/debian/gdb/gdb-6.6.dfsg/gdb/libunwind-frame.c:272: internal-error: libunwind_frame_prev_register: Assertion `regnum = 0' failed. IIRC there's a configure option you have to specify to use libunwind; maybe that's what's broken. -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
