help-gnu-emacs
[Top][All Lists]
Advanced

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

Re: Fatal error (11)


From: Thien-Thi Nguyen
Subject: Re: Fatal error (11)
Date: Mon, 25 Apr 2005 13:31:44 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Hank Chiang <address@hidden> writes:

> Program received signal SIGSEGV, Segmentation fault.
> 0xb777a46b in _XimOffKeysCheck ()
>    from /usr/lib/X11/locale/lib/common/ximcp.so.2

segv is what you get from dereferencing a NULL pointer,
or from accessing memory w/o proper privs or alignment,
or other memory-related problems.  (there is always the
random gamma ray -- unlikely if this is reproducible. :-)

after the message, the first line gives the address 
and function name of the offending code, and the second
in which file (shared object library, here) that code
is to be found.

this particular library seems to be installed as part
of the system, judging from the /usr/lib/X11 prefix,
which means you cannot easily debug it directly unless
you are prepared to build and install (under another
prefix) X11 w/ debugging support.

however, you can debug it from the emacs side.  it
looks like you have found the gdb "continue" command.
now you need to dig into the "bt" command.  for this
command to be useful, you need to build emacs w/
debugging support (normally "gcc -g" suffices).  if
you can't/won't do that, there is no point reading
the rest of this message.

the aim at this stage is to determine whether or not it
is emacs' fault or whether it is the library's fault,
so as to be able to procure a fix yourself, and/or report
the situation to the appropriate maintainers (the latter
called "spreading the joy" by curmudgeons everywhere ;-).

thi


reply via email to

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