bug#21450: 25.0.50; emacs_backtrace.txt

bug#21450: 25.0.50; emacs_backtrace.txt

[Drew Adams]

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'

bug#21450: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> 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

bug#21450: 25.0.50; emacs_backtrace.txt

[Glenn Morris]

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.

bug#21450: 25.0.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
> From: Drew Adams <drew.adams@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.

bug#21450: 25.0.50; emacs_backtrace.txt

[Dani Moncayo]

On Thu, Sep 10, 2015 at 6:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
>> From: Drew Adams <drew.adams@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

bug#21450: 25.0.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Thu, 10 Sep 2015 21:05:37 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Drew Adams <drew.adams@oracle.com>, 21450@debbugs.gnu.org
> 
> On Thu, Sep 10, 2015 at 6:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Wed, 9 Sep 2015 14:12:17 -0700 (PDT)
> >> From: Drew Adams <drew.adams@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?

bug#21450: 25.0.50; emacs_backtrace.txt

[Drew Adams]

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