From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Getting random Emacs core dumps with gnus...
Date: 02 Jan 2001 14:47:49 -0500 [thread overview]
Message-ID: <vuo7l4dhh22.fsf@csa.bu.edu> (raw)
Hi,
I've been getting random Emacs core dumps when I'm running gnus (it
happened with gnus 5.8.x from cvs and now with Oort 0.01). Luckily, I
managed to save the core file when it happened today. Issuing a
"where -v" when analyzing it in dbx gave me the following call stack:
=>[1] _libc_kill(0x0, 0xb, 0x102027ac, 0x0, 0x22134, 0x69238), at
0xfef9a790
[2] fatal_error_signal(0xb, 0x0, 0xffbedbe0, 0xfefb8000, 0x0, 0x0),
at 0x69238
[3] sigacthandler(0xb, 0x0, 0xffbedbe0, 0x0, 0x0, 0x0), at
0xfef99834
---- called from signal handler with signal 11 (SIGSEGV) ------
[4] deactivate_process(0x2a553c, 0x1fbc00, 0x1fd400, 0x10f800, 0x0,
0x0), at 0x10dd38
[5] send_process(0xffbedf90, 0x1, 0xffbee024, 0x6, 0x142364,
0x1fbc00), at 0x10fb1c
This doesn't really mean too much to me... Should I follow this up
here, or would this be considered a more general Emacs problem (if so,
where should I report it)?
Any help would be appreciated.... :-)
Thanks,
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next reply other threads:[~2001-01-02 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 19:47 Emerick Rogul [this message]
2001-01-02 20:52 ` Colin Walters
2001-01-02 21:42 ` Emerick Rogul
2001-01-02 22:29 ` Hans de Graaff
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vuo7l4dhh22.fsf@csa.bu.edu \
--to=emerick@cs.bu.edu \
/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 NNTP newsgroup(s).