GNU bug report logs - #22058
25.1.50; emacs_backtrace.txt

Previous Next

Full log

Message #17 received at 22058 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Drew Adams <drew.adams <at> oracle.com>
Cc: jwiegley <at> gmail.com, 22058 <at> debbugs.gnu.org
Subject: RE: bug#22058: 25.1.50; emacs_backtrace.txt
Date: Mon, 30 Nov 2015 08:22:44 -0800 (PST)

> > > Such a stack trace offers nothing actionable.
> >
> > Is there a simple way for me to recognize that, from the
> > backtrace?
> 
> A good rule of thumb is: if the backtrace includes this pair of lines:
> 
> > Exception 0xc0000005 at this address:
> > 774374f6
> 
> and if the address starts with 7, then we will not be able to convert
> it to any meaningful address in the Emacs application code.  (The
> exception code does not need to be 0xc0000005, although it usually
> is.)

Excellent.  Wish I'd have known that long ago.  How about mentioning
this in (emacs) `Crashing'?

Or perhaps the code that creates the emacs_backtrace.txt file could
just print a message in such a case, saying that no useful backtrace
file could be created?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.