From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: Fatal error (11)
Date: Mon, 25 Apr 2005 13:31:44 +0200 [thread overview]
Message-ID: <7e3btff5y7.fsf@ada2.unipv.it> (raw)
In-Reply-To: mailman.2870.1114394184.2895.help-gnu-emacs@gnu.org
Hank Chiang <hankchiang0911@gmail.com> 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
next parent reply other threads:[~2005-04-25 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2870.1114394184.2895.help-gnu-emacs@gnu.org>
2005-04-25 11:31 ` Thien-Thi Nguyen [this message]
2005-04-24 15:00 Fatal error (11) Hank Chiang
2005-04-25 9:10 ` Peter Dyballa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e3btff5y7.fsf@ada2.unipv.it \
--to=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).