GNU bug report logs - #17318
24.4.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 17318 in the body.
You can then email your comments to 17318 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.4.50; emacs_backtrace.txt
Date: Tue, 22 Apr 2014 20:02:54 -0700 (PDT)

Exception 0xc0000005 at this address:
0115f769

Backtrace:
01200a23
01200a94
010f448e
01166e6e
010f00df
0118865f
0118963a
011894ed
011482c8
011484c5
01148cfb
011338b4
0113465d
0113d426
010f60e7
010f4446
01118b37
01118b12
01118b6b
010011e6
764e02ff
776274fb
775e9f41




In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
 of 2014-04-21 on ODIEONE
Bzr revision: 117005 dancol <at> dancol.org-20140421180019-po4wdeg7gqvvlh5d
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 17318 <at> debbugs.gnu.org
Subject: Re: bug#17318: 24.4.50; emacs_backtrace.txt
Date: Thu, 24 Apr 2014 22:13:54 +0200

??
??:0
mark_interval at alloc.c:1333
??
??:0
??
??:0
w32_backtrace at w32fns.c:8476
emacs_abort at w32fns.c:8508
terminate_due_to_signal at emacs.c:382
die at alloc.c:6955
make_natnum at lisp.h:729
Flength at fns.c:119
concat at fns.c:524
Fcopy_sequence at fns.c:456
compile_pattern_1 at search.c:164
compile_pattern at search.c:245
fast_string_match at search.c:478
Ffind_file_name_handler at fileio.c:372
Fexpand_file_name at fileio.c:903
Fdo_auto_save at fileio.c:5553
shut_down_emacs at emacs.c:2033
terminate_due_to_signal at emacs.c:366
handle_fatal_signal at sysdep.c:1630
deliver_thread_signal at sysdep.c:1604
deliver_fatal_thread_signal at sysdep.c:1642
?? at crt1.c:0
??
??:0
??
??:0
??
??:0

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 17318 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#17318: 24.4.50; emacs_backtrace.txt
Date: Fri, 25 Apr 2014 10:05:14 +0300

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Thu, 24 Apr 2014 22:13:54 +0200
> Cc: 17318 <at> debbugs.gnu.org
> 
> mark_interval at alloc.c:1333

> w32_backtrace at w32fns.c:8476
> emacs_abort at w32fns.c:8508
> terminate_due_to_signal at emacs.c:382
> die at alloc.c:6955
> make_natnum at lisp.h:729
> Flength at fns.c:119
> concat at fns.c:524
> Fcopy_sequence at fns.c:456
> compile_pattern_1 at search.c:164
> compile_pattern at search.c:245
> fast_string_match at search.c:478
> Ffind_file_name_handler at fileio.c:372
> Fexpand_file_name at fileio.c:903
> Fdo_auto_save at fileio.c:5553
> shut_down_emacs at emacs.c:2033
> terminate_due_to_signal at emacs.c:366
> handle_fatal_signal at sysdep.c:1630
> deliver_thread_signal at sysdep.c:1604
> deliver_fatal_thread_signal at sysdep.c:1642
> ?? at crt1.c:0

Looks like a new one.  The first line shows where the original crash
happened, the rest are a secondary crash when Emacs tried to shut down
itself.

Stefan, could this be related to your latest changes in intervals.c?

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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Juanma Barranquero <lekktu <at> gmail.com>, 17318 <at> debbugs.gnu.org,
 drew.adams <at> oracle.com
Subject: Re: bug#17318: 24.4.50; emacs_backtrace.txt
Date: Fri, 25 Apr 2014 09:43:14 -0400

>> mark_interval at alloc.c:1333

>> w32_backtrace at w32fns.c:8476
>> emacs_abort at w32fns.c:8508
>> terminate_due_to_signal at emacs.c:382
>> die at alloc.c:6955
>> make_natnum at lisp.h:729
>> Flength at fns.c:119
>> concat at fns.c:524
>> Fcopy_sequence at fns.c:456
>> compile_pattern_1 at search.c:164
>> compile_pattern at search.c:245
>> fast_string_match at search.c:478
>> Ffind_file_name_handler at fileio.c:372
>> Fexpand_file_name at fileio.c:903
>> Fdo_auto_save at fileio.c:5553
>> shut_down_emacs at emacs.c:2033
>> terminate_due_to_signal at emacs.c:366
>> handle_fatal_signal at sysdep.c:1630
>> deliver_thread_signal at sysdep.c:1604
>> deliver_fatal_thread_signal at sysdep.c:1642
>> ?? at crt1.c:0

> Looks like a new one.  The first line shows where the original crash
> happened, the rest are a secondary crash when Emacs tried to shut down
> itself.

What makes you think mark_interval is where the original crash happened?

> Stefan, could this be related to your latest changes in intervals.c?

Could be, but we'd need more of the backtrace to figure out
what's happening.


        Stefan

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: lekktu <at> gmail.com, 17318 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#17318: 24.4.50; emacs_backtrace.txt
Date: Fri, 25 Apr 2014 17:11:26 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: Juanma Barranquero <lekktu <at> gmail.com>,  drew.adams <at> oracle.com,  17318 <at> debbugs.gnu.org
> Date: Fri, 25 Apr 2014 09:43:14 -0400
> 
> >> mark_interval at alloc.c:1333
> 
> >> w32_backtrace at w32fns.c:8476
> >> emacs_abort at w32fns.c:8508
> >> terminate_due_to_signal at emacs.c:382
> >> die at alloc.c:6955
> >> make_natnum at lisp.h:729
> >> Flength at fns.c:119
> >> concat at fns.c:524
> >> Fcopy_sequence at fns.c:456
> >> compile_pattern_1 at search.c:164
> >> compile_pattern at search.c:245
> >> fast_string_match at search.c:478
> >> Ffind_file_name_handler at fileio.c:372
> >> Fexpand_file_name at fileio.c:903
> >> Fdo_auto_save at fileio.c:5553
> >> shut_down_emacs at emacs.c:2033
> >> terminate_due_to_signal at emacs.c:366
> >> handle_fatal_signal at sysdep.c:1630
> >> deliver_thread_signal at sysdep.c:1604
> >> deliver_fatal_thread_signal at sysdep.c:1642
> >> ?? at crt1.c:0
> 
> > Looks like a new one.  The first line shows where the original crash
> > happened, the rest are a secondary crash when Emacs tried to shut down
> > itself.
> 
> What makes you think mark_interval is where the original crash happened?

Because the original backtrace reported by Drew said this:

  Exception 0xc0000005 at this address:
  0115f769

  Backtrace:
  01200a23
  01200a94
  ...

This is the exception handler installed by w32fns.c at work (see
my_exception_handler and globals_of_w32fns), and "Exception
0xc0000005" is invalid address exception (a.k.a. SIGSEGV).

> > Stefan, could this be related to your latest changes in intervals.c?
> 
> Could be, but we'd need more of the backtrace to figure out
> what's happening.

The only way to have more of the backtrace is to run Emacs under GDB
to begin with.  Without that, when Emacs hits a fatal exception like
that, one address is all you got.

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

From: Glenn Morris <rgm <at> gnu.org>
To: <17318-done <at> debbugs.gnu.org>
Subject: Re: bug#17318
Date: Thu, 10 Sep 2015 12:29:38 -0400

Nothing can be done with this information.

Previous Next

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