GNU bug report logs - #25990
25.1; 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 25990 in the body.
You can then email your comments to 25990 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.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

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>,
 "Phillip Lord" <phillip.lord <at> russet.org.uk>
Cc: 25990 <at> debbugs.gnu.org
Subject: Re: bug#25990: 25.1; emacs_backtrace.txt
Date: Mon, 06 Mar 2017 05:39:33 +0200

> Date: Sun, 5 Mar 2017 16:53:02 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> 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?

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

From: npostavs <at> users.sourceforge.net
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 25990 <at> debbugs.gnu.org
Subject: Re: bug#25990: 25.1; emacs_backtrace.txt
Date: Sun, 05 Mar 2017 23:08:57 -0500

Drew Adams <drew.adams <at> oracle.com> writes:

> Dunno whether this backtrace from an emacs -Q session helps:

Is there any reason to think this is not another case of #23935?

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

From: Drew Adams <drew.adams <at> oracle.com>
To: npostavs <at> users.sourceforge.net
Cc: 25990 <at> debbugs.gnu.org
Subject: RE: bug#25990: 25.1; emacs_backtrace.txt
Date: Sun, 5 Mar 2017 20:49:58 -0800 (PST)

> Is there any reason to think this is not another case of #23935?

It's from Emacs 25.1-2, at least.

#23935 was from "Emacs 25.1.50.1 (i686-pc-mingw32) of 2015-12-10".

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

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 25990 <at> debbugs.gnu.org
Subject: Re: bug#25990: 25.1; emacs_backtrace.txt
Date: Mon, 6 Mar 2017 09:06:56 -0500

On Sun, Mar 5, 2017 at 11:49 PM, Drew Adams <drew.adams <at> oracle.com> wrote:
>> Is there any reason to think this is not another case of #23935?
>
> It's from Emacs 25.1-2, at least.
>
> #23935 was from "Emacs 25.1.50.1 (i686-pc-mingw32) of 2015-12-10".

#24692 which is the same, was reported from 25.1

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 25990 <at> debbugs.gnu.org
Subject: RE: bug#25990: 25.1; emacs_backtrace.txt
Date: Mon, 6 Mar 2017 07:03:53 -0800 (PST)

> >> Is there any reason to think this is not another case of #23935?
> >
> > It's from Emacs 25.1-2, at least.
> >
> > #23935 was from "Emacs 25.1.50.1 (i686-pc-mingw32) of 2015-12-10".
> 
> #24692 which is the same, was reported from 25.1

There was no backtrace for #24692.  Instead, there is a recipe
to repro.  There is no recipe to repro #25990, but there is a
backtrace.

I can't tell that they are similar or the same, but if you
can determine that, please feel free to merge or close, as
you see fit.  Thx.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: npostavs <at> users.sourceforge.net
Cc: 25990 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#25990: 25.1; emacs_backtrace.txt
Date: Mon, 06 Mar 2017 18:06:00 +0200

> From: npostavs <at> users.sourceforge.net
> Date: Sun, 05 Mar 2017 23:08:57 -0500
> Cc: 25990 <at> debbugs.gnu.org
> 
> Drew Adams <drew.adams <at> oracle.com> writes:
> 
> > Dunno whether this backtrace from an emacs -Q session helps:
> 
> Is there any reason to think this is not another case of #23935?

Without any details of what was Drew doing when this happens, I don't
see how we could assume anything here.

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>, npostavs <at> users.sourceforge.net
Cc: 25990 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: RE: bug#25990: 25.1; emacs_backtrace.txt
Date: Mon, 6 Mar 2017 08:11:41 -0800 (PST)

> > > Dunno whether this backtrace from an emacs -Q session helps:
> >
> > Is there any reason to think this is not another case of #23935?
> 
> Without any details of what was Drew doing when this happens, I don't
> see how we could assume anything here.

There are no details.  It happened at a seemingly random moment.
I cannot say what was the last thing I did before the crash.  Sorry.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25990-done <at> debbugs.gnu.org, drew.adams <at> oracle.com,
 phillip.lord <at> russet.org.uk
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 <eliz <at> gnu.org>
> Cc: 25990 <at> debbugs.gnu.org
> 
> > Date: Sun, 5 Mar 2017 16:53:02 -0800 (PST)
> > From: Drew Adams <drew.adams <at> oracle.com>
> > 
> > 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.

Previous Next

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