GNU bug report logs - #21450
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 21450 in the body.
You can then email your comments to 21450 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: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)

More recent build.  Dunno whether this helps more.

Exception 0xc0000005 at this address:
752674f6

Backtrace:
011ad0d1



In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-08-16 on LEG570
Bzr revision: f7ee23e587b01f179284b5554c67d579a2def676
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'

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

From: Drew Adams <drew.adams <at> oracle.com>
To: 21450 <at> debbugs.gnu.org
Subject: RE: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Wed, 9 Sep 2015 14:16:11 -0700 (PDT)

> More recent build.  Dunno whether this helps more.
> 
> Exception 0xc0000005 at this address:
> 752674f6
> 
> Backtrace:
> 011ad0d1
> 
> In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
>  of 2015-08-16 on LEG570
> Bzr revision: f7ee23e587b01f179284b5554c67d579a2def676
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'


Sorry, this is the build for this crash.  (I sent the bug report
from the 2015-08-16 build.)

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-09-05
Repository revision: 2330ca33a97867f2ea1123bcf7bfe5cfcc030b36
Windowing system distributor 'Microsoft Corp.', version 6.1.7601
Configured using:
 'configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS

Message #13 received at 21450-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 21450-done <at> debbugs.gnu.org
Subject: Re: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Thu, 10 Sep 2015 12:17:28 -0400

Drew Adams wrote:

> More recent build.  Dunno whether this helps more.
>
> Exception 0xc0000005 at this address:
> 752674f6
>
> Backtrace:
> 011ad0d1

It doesn't help. Isn't it obvious that this is not actionable?

Please either stop making such reports, or learn how to compile Emacs
and run it under a debugger. Anything else is just a waste of everyone's
time.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 21450 <at> debbugs.gnu.org
Subject: Re: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Thu, 10 Sep 2015 19:51:45 +0300

> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> More recent build.  Dunno whether this helps more.
> 
> Exception 0xc0000005 at this address:
> 752674f6
> 
> Backtrace:
> 011ad0d1

No, it's also stripped.

Maybe Dany can convert these addresses to something human-readable.

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

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 21450 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Thu, 10 Sep 2015 21:05:37 +0200

On Thu, Sep 10, 2015 at 6:51 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
>> From: Drew Adams <drew.adams <at> oracle.com>
>>
>> More recent build.  Dunno whether this helps more.
>>
>> Exception 0xc0000005 at this address:
>> 752674f6
>>
>> Backtrace:
>> 011ad0d1
>
> No, it's also stripped.
>
> Maybe Dany can convert these addresses to something human-readable.

$ addr2line -psf -e ./emacs.exe < ./foo
?? ??:0
?? ??:0
?? ??:0
?? ??:0
w32_backtrace at w32fns.c:9388

-- 
Dani Moncayo

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: 21450 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Thu, 10 Sep 2015 22:21:43 +0300

> Date: Thu, 10 Sep 2015 21:05:37 +0200
> From: Dani Moncayo <dmoncayo <at> gmail.com>
> Cc: Drew Adams <drew.adams <at> oracle.com>, 21450 <at> debbugs.gnu.org
> 
> On Thu, Sep 10, 2015 at 6:51 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
> >> From: Drew Adams <drew.adams <at> oracle.com>
> >>
> >> More recent build.  Dunno whether this helps more.
> >>
> >> Exception 0xc0000005 at this address:
> >> 752674f6
> >>
> >> Backtrace:
> >> 011ad0d1
> >
> > No, it's also stripped.
> >
> > Maybe Dany can convert these addresses to something human-readable.
> 
> $ addr2line -psf -e ./emacs.exe < ./foo
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> w32_backtrace at w32fns.c:9388

Thanks.

Unfortunately, the important address, 752674f6, was not translated, so
there's nothing that can be done with this.

Drew, is this repeatable?  If so, can you provide a recipe?

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Dani Moncayo <dmoncayo <at> gmail.com>
Cc: 21450 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: RE: bug#21450: 25.0.50; emacs_backtrace.txt
Date: Thu, 10 Sep 2015 12:30:48 -0700 (PDT)

> Unfortunately, the important address, 752674f6, was not translated, so
> there's nothing that can be done with this.
> 
> Drew, is this repeatable?  If so, can you provide a recipe?

I get this crash or similar all the time now (aka often), with this
build, but no, I don't have a recipe.  If I can figure out something
about the context I'll let you know, but feel free to leave the bug
closed in the meantime.

No idea whether it is related, but I also have *lots* of frame
sizing problems with this build (much more than before, where
since 2014-10-20 I've had sizing problems with thumbnail frames
and some with normal-size frames).

I see that there is a lot of bug-list correspondence between
Martin and Keith these days about some frame size things, and
I'm hoping that with a little luck some of my frame problems
will go away by the time I get a new Windows binary, thanks to
their efforts. ;-)

Again, no idea whether my recent frame problems have anything to
do with these recent crashes.  Just thought I'd mention it, in
case someone sees something similar or it rings a bell.

Previous Next

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