GNU bug report logs - #22502
25.0.90; 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 22502 in the body.
You can then email your comments to 22502 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.90; emacs_backtrace.txt
Date: Sun, 31 Jan 2016 09:00:54 -0800 (PST)

This is with the Emacs 25.1 pretest -

Backtrace:
0000000400174400
000000040017449a
00000004000a609a
00000004000be186
00000004000beeb4
00000004001c4a18
0000000076d68000
0000000076d79055
0000000076d68c07
0000000076d9d940
000007fefeda51a7


In GNU Emacs 25.0.90.2 (x86_64-w64-mingw32)
 of 2016-01-30
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/tmp/emacs --without-dbus --without-imagemagick
 'CFLAGS=-O2 -fomit-frame-pointer -g0' 'LDFLAGS=-static-libgcc
 -static-libstdc++ -static -s -Wl,-s''

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 22502-done <at> debbugs.gnu.org
Subject: Re: bug#22502: 25.0.90; emacs_backtrace.txt
Date: Sun, 31 Jan 2016 20:24:23 +0200

> Date: Sun, 31 Jan 2016 09:00:54 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> This is with the Emacs 25.1 pretest -
> 
> Backtrace:
> 0000000400174400
> 000000040017449a
> 00000004000a609a
> 00000004000be186
> 00000004000beeb4
> 00000004001c4a18
> 0000000076d68000
> 0000000076d79055
> 0000000076d68c07
> 0000000076d9d940
> 000007fefeda51a7
> 
> 
> In GNU Emacs 25.0.90.2 (x86_64-w64-mingw32)
>  of 2016-01-30
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --prefix=/tmp/emacs --without-dbus --without-imagemagick
>  'CFLAGS=-O2 -fomit-frame-pointer -g0' 'LDFLAGS=-static-libgcc
>  -static-libstdc++ -static -s -Wl,-s''
                             ^^^^^^^^^
Whoever built that binary, stripped the symbols (see the "-s" switch
above), so any such reports are useless, as no one can ever do
anything with them.  Too bad.

Would the person who is building these binaries please refrain from
using switches that are hostile to debugging, such as
-fomit-frame-pointer and -s?

Closing.

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

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: 22502 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Drew Adams <drew.adams <at> oracle.com>
Subject: 25.0.90; emacs_backtrace.txt
Date: Mon, 01 Feb 2016 14:31:04 +0000

[Message part 1 (text/plain, inline)]

Hi Drew,

I opened a ticket for the emacsbinw64 project on sourceforge and the dev
(Chris Zheng) was kind enough to create a new build without the flags that
Eli pointed out:

Check out https://sourceforge.net/p/emacsbinw64/tickets/9/ You can download
the latest pretest build from here:
https://sourceforge.net/projects/emacsbinw64/files/pretest/

I was able to extract the .7z and run it fine on Windows 7. I do not work
in Windows so you would be the right candidate to try it out again and see
if it still crashes.

@Eli: Would you be able to help Chris with his concern about contributing
official Windows builds? What responsibilities do the "builders" need to
carry?

[Message part 2 (text/html, inline)]

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Kaushal Modi <kaushal.modi <at> gmail.com>, 22502 <at> debbugs.gnu.org, Eli
 Zaretskii <eliz <at> gnu.org>
Subject: RE: 25.0.90; emacs_backtrace.txt
Date: Mon, 1 Feb 2016 07:12:02 -0800 (PST)

[Message part 1 (text/plain, inline)]

Hi Kaushal,

 

Thanks for this. I'm downloading it now. I see that in the first two hours it has been available 421 people have already downloaded it!

 

Thx - Drew

 

Hi Drew,

 

I opened a ticket for the emacsbinw64 project on sourceforge and the dev (Chris Zheng) was kind enough to create a new build without the flags that Eli pointed out:

 

Check out https://sourceforge.net/p/emacsbinw64/tickets/9/ You can download the latest pretest build from here: https://sourceforge.net/projects/emacsbinw64/files/pretest/

 

I was able to extract the .7z and run it fine on Windows 7. I do not work in Windows so you would be the right candidate to try it out again and see if it still crashes.

 

@Eli: Would you be able to help Chris with his concern about contributing official Windows builds? What responsibilities do the "builders" need to carry?

[Message part 2 (text/html, inline)]

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kaushal Modi <kaushal.modi <at> gmail.com>
Cc: 22502 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: 25.0.90; emacs_backtrace.txt
Date: Mon, 01 Feb 2016 21:23:17 +0200

> From: Kaushal Modi <kaushal.modi <at> gmail.com>
> Date: Mon, 01 Feb 2016 14:31:04 +0000
> 
> @Eli: Would you be able to help Chris with his concern about contributing official Windows builds? What
> responsibilities do the "builders" need to carry?

Basically, answer questions and perhaps rebuilding from time to time
if some issues come up.  Bonus points for producing human-readable
backtraces from addresses in emacs_backtrace.txt posted to the bug
tracker, by running addr2line on the addresses (the exact command is
documented in the Emacs manual).

Thanks.

Previous Next

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