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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21673 in the body.
You can then email your comments to 21673 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.50; emacs_backtrace.txt
Date: Mon, 12 Oct 2015 11:33:39 -0700 (PDT)

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



In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-10-06
Bzr revision: a4a98a1b2568793ead43e824ecf227768759df12
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''

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

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 21673 <at> debbugs.gnu.org
Subject: Re: bug#21673: 25.0.50; emacs_backtrace.txt
Date: Wed, 30 Dec 2015 11:55:04 +0100

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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.