bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash in `i frame'


From: Eli Zaretskii
Subject: Re: Crash in `i frame'
Date: Mon, 24 Jul 2006 22:23:05 +0300

> From: Richard Stallman <address@hidden>
> Date: Sun, 23 Jul 2006 01:27:11 -0400
> 
> 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.

GDB 6.5 was released recently; please try that.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]