[debbugs-tracker] bug#25990: closed (25.1; emacs_backtrace.txt)

[GNU bug Tracking System]

Your message dated Tue, 07 Mar 2017 17:40:38 +0200
with message-id <address@hidden>
and subject line Re: bug#25990: 25.1; emacs_backtrace.txt
has caused the debbugs.gnu.org bug report #25990,
regarding 25.1; emacs_backtrace.txt
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25990: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25990
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.1; emacs_backtrace.txt
>
>
>
>
> Date: 
>
> Sun, 5 Mar 2017 16:53:02 -0800 (PST)
>
>
>
>
> Dunno whether this backtrace from an emacs -Q session helps:
>
> Backtrace:
> 0000000400174f80
> 000000040017501a
> 00000004000a629a
> 00000004000be496
> 00000004000bf1c4
> 00000004001c5628
> 0000000076d07950
> 0000000076d18125
> 0000000076d08557
> 0000000076d3bcb0
> 000007fefe575227
>
>
> In GNU Emacs 25.1.1 (x86_64-w64-mingw32)
>  of 2016-11-15 built on LAPHROAIG
> Windowing system distributor 'Microsoft Corp.', version 6.1.7601
> Configured using:
>  'configure --without-dbus --without-compress-install 'CFLAGS=-O2
>  -static -g3''
>
> Configured features:
> XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
> TOOLKIT_SCROLL_BARS
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#25990: 25.1; emacs_backtrace.txt
>
>
>
>
> Date: 
>
> Tue, 07 Mar 2017 17:40:38 +0200
>
>
>
>
> > Date: Mon, 06 Mar 2017 05:39:33 +0200
> > From: Eli Zaretskii <address@hidden>
> > Cc: address@hidden
> > 
> > > Date: Sun, 5 Mar 2017 16:53:02 -0800 (PST)
> > > From: Drew Adams <address@hidden>
> > > 
> > > Dunno whether this backtrace from an emacs -Q session helps:
> > > 
> > > Backtrace:
> > > 0000000400174f80
> > > 000000040017501a
> > > 00000004000a629a
> > > 00000004000be496
> > > 00000004000bf1c4
> > > 00000004001c5628
> > > 0000000076d07950
> > > 0000000076d18125
> > > 0000000076d08557
> > > 0000000076d3bcb0
> > > 000007fefe575227
> > > 
> > > 
> > > In GNU Emacs 25.1.1 (x86_64-w64-mingw32)
> > >  of 2016-11-15 built on LAPHROAIG
> > 
> > Phillip, can you convert this to file names and line numbers, please?
>
> Never mind, I did it myself:
>
>   w32_backtrace at 
> C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/w32fns.c:9804
>   emacs_abort at 
> C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/w32fns.c:9836
>   terminate_due_to_signal at 
> C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/emacs.c:376
>   handle_fatal_signal at 
> C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/sysdep.c:1601
>   deliver_thread_signal at 
> C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/sysdep.c:1559
>   _gnu_exception_handler at 
> C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crt_handler.c:220
>
> This means that the information about the actual locus of the crash is
> lost, and there's nothing that can be done about this report.  So I'm
> closing it.
>
> Once again, if Drew wants these crashes to be investigated and solved,
> he will find a way to run Emacs under GDB and report more useful
> information about crashes.
>
>
> --- End Message ---