Crash in `i frame'

Thread View: gnu.gdb.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Richard Stallman Sun, 23 Jul 2006 05:27

#1224

Author: Richard Stallman
Date: Sun, 23 Jul 2006 05:27

16 lines
2114 bytes

In GDB 6.4 on GNU/Linux, I did `i frame' after a strange Emacs crash
involving stack clobberage.  The command did not work, reporting
"internal error" in dwarf-frame2.c:676.  (I am typing this from
memory; I can't be sure of the file name, but the line number was
definitely 676.)

The selected frame was the innermost one, and was calling
__kernel_vsyscall (that may not be the precise spelling).

`i frame' is a low-level command for last resort examination of the
stack, in comfusing cases.  It must be written defensively, so that it
_always_ works, no matter how unreasonable the data is.  It must never
report "internal error"; it must do something reasonable, no matter
what data it finds.

Please ack when this is fixed -- it is very important.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads