bug#22502: 25.0.90; emacs_backtrace.txt

bug#22502: 25.0.90; emacs_backtrace.txt

[Drew Adams]

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

bug#22502: 25.0.90; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Sun, 31 Jan 2016 09:00:54 -0800 (PST)
> From: Drew Adams <drew.adams@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.

bug#22502: 25.0.90; emacs_backtrace.txt

[Kaushal Modi]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 941 bytes --]

bug#22502: 25.0.90; emacs_backtrace.txt

[Drew Adams]

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 3927 bytes --]

bug#22502: 25.0.90; emacs_backtrace.txt

[Eli Zaretskii]

> From: Kaushal Modi <kaushal.modi@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.