GNU bug report logs - #21673
25.0.50; emacs_backtrace.txt

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Cc: 21673 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#21673: 25.0.50; emacs_backtrace.txt
Date: Wed, 30 Dec 2015 18:03:16 +0200

> From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
> Date: Wed, 30 Dec 2015 11:55:04 +0100
> Cc: 21673 <at> debbugs.gnu.org
> 
> Drew Adams <drew.adams <at> oracle.com> writes:
> 
> > Looks similar, but not identical, to bug #21655.  The build is the same.
> >
> > Exception 0xc0000005 at this address:
> > 76fd74f6
> >
> > Backtrace:
> > 012286fc
> > 0122876d
> > 011052ba
> > 0112bf84
> > 0112bf5f
> > 0112bfb8
> > 010010f5
> > 76ee02ff
> > 77e3344b
> > 77df9851
> 
> This is the final unresponded-to emacs_backtrace.txt bug report, you'll
> all probably be relieved to hear.  :-)
> 
> Is there anything further to do here?

No.  The high address where the exception happened means it was some
DLL, either a system DLL or some optional DLL loaded by Emacs.  So
without GDB backtrace, there's nothing we can do to even find out
which library crashed, let alone where and why.

Previous Next

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