GNU bug report logs - #13140
24.3.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 13140 in the body.
You can then email your comments to 13140 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: 24.3.50; emacs_backtrace.txt
Date: Tue, 11 Dec 2012 07:49:33 -0800

Backtrace:
0x01154B7D
0x01154BEF
0x01001459
0x0102190E
0x0114A734
0x7E418730
0x7E418812
0x7E4189C9
0x7E418A0C
0x01148D5C
0x01148FFB
0x7C80B725
 
BTW, ever since the introduction of the emacs_backtrace.txt files, when I get a
crash now I get TWO fatal-error dialog boxes, not one.  One is on top of the
other (staggered slightly), and interacting with the top one (I click No)
removes both of them and ends Emacs (closes all frames).
 
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
 of 2012-12-07 on MS-W7-DANI
Bzr revision: 111150 eggert <at> cs.ucla.edu-20121207175317-wxhrqxpp0173whq0
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
 -Ic:/emacs/libs/libXpm-3.5.10/include -Ic:/emacs/libs/libXpm-3.5.10/src
 -Ic:/emacs/libs/libpng-1.2.37-lib/include -Ic:/emacs/libs/zlib-1.2.5
 -Ic:/emacs/libs/giflib-4.1.4-1-lib/include
 -Ic:/emacs/libs/jpeg-6b-4-lib/include
 -Ic:/emacs/libs/tiff-3.8.2-1-lib/include
 -Ic:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
 -Ic:/emacs/libs/gnutls-3.0.9-w32-bin/include
 -Ic:/emacs/libs/libiconv-1.9.2-1-lib/include'
 

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 13140 <at> debbugs.gnu.org
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Tue, 11 Dec 2012 17:59:25 +0200

> From: "Drew Adams" <drew.adams <at> oracle.com>
> Date: Tue, 11 Dec 2012 07:49:33 -0800
> 
> BTW, ever since the introduction of the emacs_backtrace.txt files, when I get a
> crash now I get TWO fatal-error dialog boxes, not one.  One is on top of the
> other (staggered slightly), and interacting with the top one (I click No)
> removes both of them and ends Emacs (closes all frames).

This means Emacs gets a second fatal error while processing the first
one.

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Eli Zaretskii'" <eliz <at> gnu.org>
Cc: 13140 <at> debbugs.gnu.org
Subject: RE: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Tue, 11 Dec 2012 19:10:04 -0800

> > BTW, ever since the introduction of the emacs_backtrace.txt 
> > files, when I get a crash now I get TWO fatal-error dialog
> > boxes, not one.  One is on top of the other (staggered
> > slightly), and interacting with the top one (I click No)
> > removes both of them and ends Emacs (closes all frames).
> 
> This means Emacs gets a second fatal error while processing
> the first one.

OK, well it seems to happen systematically - ever since the introduction of
emacs_backtrace.txt.  Dunno if others are seeing this, but IIRC I've seen it
each time Emacs created a backtrace file.

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Eli Zaretskii'" <eliz <at> gnu.org>
Cc: 13140 <at> debbugs.gnu.org
Subject: RE: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Tue, 11 Dec 2012 19:56:05 -0800

I didn't pay attention that the backtraces I got today were in fact identical.
Sorry about that.  (I keep getting them.)

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 13140 <at> debbugs.gnu.org
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 05:58:52 +0200

> From: "Drew Adams" <drew.adams <at> oracle.com>
> Cc: <13140 <at> debbugs.gnu.org>
> Date: Tue, 11 Dec 2012 19:10:04 -0800
> 
> > > BTW, ever since the introduction of the emacs_backtrace.txt 
> > > files, when I get a crash now I get TWO fatal-error dialog
> > > boxes, not one.  One is on top of the other (staggered
> > > slightly), and interacting with the top one (I click No)
> > > removes both of them and ends Emacs (closes all frames).
> > 
> > This means Emacs gets a second fatal error while processing
> > the first one.
> 
> OK, well it seems to happen systematically - ever since the introduction of
> emacs_backtrace.txt.  Dunno if others are seeing this, but IIRC I've seen it
> each time Emacs created a backtrace file.

It never happened to me.

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

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 13140 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 08:31:20 +0100

>> > > BTW, ever since the introduction of the emacs_backtrace.txt
>> > > files, when I get a crash now I get TWO fatal-error dialog
>> > > boxes, not one.  One is on top of the other (staggered
>> > > slightly), and interacting with the top one (I click No)
>> > > removes both of them and ends Emacs (closes all frames).
>> >
>> > This means Emacs gets a second fatal error while processing
>> > the first one.
>>
>> OK, well it seems to happen systematically - ever since the introduction of
>> emacs_backtrace.txt.  Dunno if others are seeing this, but IIRC I've seen it
>> each time Emacs created a backtrace file.
>
> It never happened to me.

In case this is somehow due to a defect in the build I made [1], it
would be good that someone made and upload a build of the current
trunk, so that Drew could try it and see if the crashes happen then
too.


--------------

[1] Although the last one was made with a clean bootstrap, but who knows.

-- 
Dani Moncayo

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

From: Glenn Morris <rgm <at> gnu.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 13140 <at> debbugs.gnu.org
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 03:14:56 -0500

Dani Moncayo wrote:

> In case this is somehow due to a defect in the build I made [1], it
> would be good that someone made and upload a build of the current
> trunk, so that Drew could try it and see if the crashes happen then
> too.

Why do some people on MS Windows find it impossible to build Emacs for
themselves?

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 13140 <at> debbugs.gnu.org, Dani Moncayo <dmoncayo <at> gmail.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 16:20:52 +0100

On Wed, Dec 12, 2012 at 9:14 AM, Glenn Morris <rgm <at> gnu.org> wrote:

> Why do some people on MS Windows find it impossible to build Emacs for
> themselves?

Not impossible, but Windows users do not have a package manager to
ease downloading all the required tools (compiler and build
environment, plus image libraries, some unix-style tools, etc.). If
the user does not really need all these except to compile Emacs, it's
understandable that some or many of them will chose to avoid the
hassle and rely on prepackaged binaries.

    Juanma

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Glenn Morris'" <rgm <at> gnu.org>, "'Dani Moncayo'" <dmoncayo <at> gmail.com>
Cc: 13140 <at> debbugs.gnu.org
Subject: RE: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 08:18:12 -0800

> > In case this is somehow due to a defect in the build I made [1], it
> > would be good that someone made and upload a build of the current
> > trunk, so that Drew could try it and see if the crashes happen then
> > too.
> 
> Why do some people on MS Windows find it impossible to build Emacs for
> themselves?

How could anyone answer wrt your hypothetical "some people"?  And are you
perhaps presuming that anyone who does not build Emacs "finds it impossible" to
do so?

What is your real problem about this?  And how is it related to fixing the bug
reported in this thread?

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 13140 <at> debbugs.gnu.org,
	Dani Moncayo Melgar <dmoncayo <at> gmail.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 19:11:56 +0100

On Wed, Dec 12, 2012 at 8:31 AM, Dani Moncayo <dmoncayo <at> gmail.com> wrote:

> In case this is somehow due to a defect in the build I made [1], it
> would be good that someone made and upload a build of the current
> trunk, so that Drew could try it and see if the crashes happen then
> too.

Drew, if you're interested you can grab a build from today's trunk at
https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99

    Juanma

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Juanma Barranquero'" <lekktu <at> gmail.com>
Cc: 'Eli Zaretskii' <eliz <at> gnu.org>, 13140 <at> debbugs.gnu.org,
	'Dani Moncayo Melgar' <dmoncayo <at> gmail.com>
Subject: RE: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Wed, 12 Dec 2012 10:14:42 -0800

> Drew, if you're interested you can grab a build from today's trunk at
> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99

Thanks, Juanma.  I'll pick it up tonight after work.

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

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 13140 <at> debbugs.gnu.org,
	Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Thu, 13 Dec 2012 20:53:41 +0100

>> In case this is somehow due to a defect in the build I made [1], it
>> would be good that someone made and upload a build of the current
>> trunk, so that Drew could try it and see if the crashes happen then
>> too.
>
> Drew, if you're interested you can grab a build from today's trunk at
> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99

Juanma, did you configure with "--enable-checking" ?

I ask this because I configured with it, and IIUC, these backtraces
that Drew is getting are due to assertions which are enabled only if
Emacs was configured with that option.

OTOH, I also passed "--no-opt" to the configure script, which perhaps
might make a difference too.

-- 
Dani Moncayo

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

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 13140 <at> debbugs.gnu.org,
	Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Thu, 13 Dec 2012 21:04:30 +0100

>>> In case this is somehow due to a defect in the build I made [1], it
>>> would be good that someone made and upload a build of the current
>>> trunk, so that Drew could try it and see if the crashes happen then
>>> too.
>>
>> Drew, if you're interested you can grab a build from today's trunk at
>> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99
>
> Juanma, did you configure with "--enable-checking" ?
>
> I ask this because I configured with it, and IIUC, these backtraces
> that Drew is getting are due to assertions which are enabled only if
> Emacs was configured with that option.
>
> OTOH, I also passed "--no-opt" to the configure script, which perhaps
> might make a difference too.

Answering myself: yes, you used both of those options:

  In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
   of 2012-12-13 on ODIEONE
  Bzr revision: 111211 eggert <at> cs.ucla.edu-20121213021749-eyqqen0ewhn2hogq
  Windowing system distributor `Microsoft Corp.', version 5.1.2600
  Configured using:
   `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
   -IC:/Devel/emacs/build/include -Wall -Wextra -Wno-sign-compare
   -Wno-type-limits -Wno-missing-field-initializers -Wno-pointer-sign
   -Wdeclaration-after-statement --ldflags -LC:/Devel/emacs/build/lib'


So, if Drew doesn't get this backtrace again, I guess that the problem
is in my build (unless it was an error in code, fixed between your bzr
revision and mine).  But I don't know what I'm doing wrong...

-- 
Dani Moncayo

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

From: martin rudalics <rudalics <at> gmx.at>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: Juanma Barranquero <lekktu <at> gmail.com>, 13140 <at> debbugs.gnu.org
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Fri, 14 Dec 2012 11:24:51 +0100

> I ask this because I configured with it, and IIUC, these backtraces
> that Drew is getting are due to assertions which are enabled only if
> Emacs was configured with that option.

Practically all backtraces Drew sent come from broken assertions.

martin

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

From: Glenn Morris <rgm <at> gnu.org>
To: 13140 <at> debbugs.gnu.org
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Fri, 22 Feb 2013 20:08:46 -0500

AFAICS, nobody ever decoded this backtrace; so nothing can be done.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: Juanma Barranquero <lekktu <at> gmail.com>, 13140 <at> debbugs.gnu.org,
 Eli Zaretskii <eliz <at> gnu.org>, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Sun, 09 Feb 2014 20:47:03 -0800

Dani Moncayo <dmoncayo <at> gmail.com> writes:

> Answering myself: yes, you used both of those options:
>
>   In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
>    of 2012-12-13 on ODIEONE
>   Bzr revision: 111211 eggert <at> cs.ucla.edu-20121213021749-eyqqen0ewhn2hogq
>   Windowing system distributor `Microsoft Corp.', version 5.1.2600
>   Configured using:
>    `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
>    -IC:/Devel/emacs/build/include -Wall -Wextra -Wno-sign-compare
>    -Wno-type-limits -Wno-missing-field-initializers -Wno-pointer-sign
>    -Wdeclaration-after-statement --ldflags -LC:/Devel/emacs/build/lib'
>
> So, if Drew doesn't get this backtrace again, I guess that the problem
> is in my build (unless it was an error in code, fixed between your bzr
> revision and mine).  But I don't know what I'm doing wrong...

This was a year ago, so I'm closing this bug because it's thought that
it might be a build issue.  Please reopen if still present.

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

Previous Next

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