Fatal exceptions...

Fatal exceptions...

[Emerick Rogul]

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

Re: Fatal exceptions...

[Simon Josefsson]

Emerick Rogul <emerick@csa.bu.edu> writes:

> 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?

M-x toggle-debug-on-error RET before starting Gnus might give you more
details.  (If you mean a elisp error, I do not know the term fatal
exception.)

Re: Fatal exceptions...

[Kai Großjohann]

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...

kai
-- 
I like BOTH kinds of music.

Re: Fatal exceptions...

[Emerick Rogul]

Simon Josefsson writes:

: Emerick Rogul <emerick@csa.bu.edu> writes:
:: 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?

: M-x toggle-debug-on-error RET before starting Gnus might give you more
: details.  (If you mean a elisp error, I do not know the term fatal
: exception.)

Ah, OK.  I'll give that a try, it can't hurt...  :-)

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul        /\/  "...i saw your girlfriend and she's eating her
emerick@cs.bu.edu    /\/   fingers like they're just another meal."
------------------------------------------------- 'summer babe', pavement

Re: Fatal exceptions...

[Emerick Rogul]

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