[Top][All Lists]

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

Re: Emacs 21.1.1 segmentation fault (!)

From: Richard Stallman
Subject: Re: Emacs 21.1.1 segmentation fault (!)
Date: Tue, 18 Dec 2001 14:17:59 -0700 (MST)

    Hmm... I'm not getting completely consistent output from gdb; it may
    be that the code optimization confused things.  E.g. the value of
    row->glyphs[area][i].object is 0x3849F31C.  The type of this value is
    0x03, which is not Lisp_Vectorlike, and yet the assembly code appears
    to indicate that we're dying inside of an evalation of code generated

Even though it is not a vectorlike object, if it is a valid string the
code to fetch the size of it as if it were a vectorlike ought not to
crash.  It ought to fetch data out of the string.

Is that object valid as a string?  Or is the address 849f31c nonsense?
What does the xstring command print about that "string"?

    According to gdb, the value of %edx here is 0xbfffe7cc, which is not
    an invalid address, but I don't believe this is the correct value of
    %edx at the time of the fault since gdb's "info reg" reports the same
    value for all frames;

That's correct.  %edx is not a saved register, so it is clobbered by
every function call.  It should be saved by entry to the signal
handler, but GDB may not know how to figure out what's going on in
the signal handler.

reply via email to

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