From: Emerick Rogul <emerick@csa.bu.edu>
Subject: Fatal exceptions...
Date: 13 Oct 2000 14:53:08 -0400 [thread overview]
Message-ID: <vuon1g8d14b.fsf@csa.bu.edu> (raw)
Hi,
I'm getting a lot of fatal exceptions when running gnus lately (one or
two per day, which is "a lot" when you're used to none :-). I can't
figure out if I'm doing anything wrong, because they seem to happen at
random times.
I'm using the latest cvs version of gnus and Emacs 20.4.1 on Solaris.
Is there something I can run when I launch gnus that will let me
easily capture some details about the stack when I get a fatal
exception?
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "i've said many, many, many unkind things about
emerick@cs.bu.edu /\/ philadelphia, and i meant every one of them."
----------------------------------------------------------- david lynch
next reply other threads:[~2000-10-13 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-13 18:53 Emerick Rogul [this message]
2000-10-13 20:44 ` Simon Josefsson
2000-10-13 21:33 ` Emerick Rogul
2000-10-13 20:46 ` Kai Großjohann
2000-10-13 21:36 ` Emerick Rogul
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=vuon1g8d14b.fsf@csa.bu.edu \
--to=emerick@csa.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).