Gnus development mailing list
 help / color / mirror / Atom feed
From: Emerick Rogul <emerick@csa.bu.edu>
Subject: Re: Fatal exceptions...
Date: 13 Oct 2000 17:36:07 -0400	[thread overview]
Message-ID: <vuo66mwifug.fsf@csa.bu.edu> (raw)
In-Reply-To: <vafaec8qxj0.fsf@lucy.cs.uni-dortmund.de>

Kai Großjohann writes:

: On 13 Oct 2000, Emerick Rogul wrote:
:: 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?

: Did you compile Emacs with debugging information (the compiler switch
: is probably `-g')?  Then you can run Emacs under the debugger, then
: use that to get a backtrace.

: Since you get several exceptions per day, you won't need to run Emacs
: under the debugger for too long...

Unfortunately, this is a University account I'm using, and I don't
think they built Emacs with debugging information.  I have limited
space on here, otherwise I'd try experimenting with building my own
version.

Oh well...I'll try to see if I can better pinpoint when it happens.

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul         /\/  "the doctor smiles terribly.  'i am referring
emerick@cs.bu.edu     /\/   your case directly to the coroner.'"
------------------------------------- 'naked lunch', william s. burroughs



      reply	other threads:[~2000-10-13 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-13 18:53 Emerick Rogul
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 [this message]

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=vuo66mwifug.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).