GNU bug report logs - #16511
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 16511 in the body.
You can then email your comments to 16511 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: Mon, 20 Jan 2014 16:18:53 -0800 (PST)

Here is a different one, which I got with my setup.  I will soon give up
trying to use this build, though, so I probably won't be finding any
more of these.

Exception 0xc0000005 at this address:
011606f0

Backtrace:
011fb4d1
011fb542
010efd72
01161c41
010eba4b
01183452
0118442d
011842e0
01143688
01143885
011440bb
0112ed6c
0112fb15
01138872
010f19a1
010efd2a
01114348
01114323
0111437c
010011e6
762ffff7
777074fb
776c9f41




In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-01-17 on ODIEONE
Bzr revision: 116059 michael.albinus <at> gmx.de-20140117182409-gz695p2c951idlee
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16511 <at> debbugs.gnu.org
Subject: Re: bug#16511: 24.3.50; emacs_backtrace.txt
Date: Tue, 21 Jan 2014 03:56:18 +0100

??
??:0
mark_object at alloc.c:5955
??
??:0
??
??:0
w32_backtrace at w32fns.c:8383
emacs_abort at w32fns.c:8415
terminate_due_to_signal at emacs.c:378
die at alloc.c:6761
make_natnum at lisp.h:736
Flength at fns.c:110
concat at fns.c:515
Fcopy_sequence at fns.c:447
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:5566
shut_down_emacs at emacs.c:2017
terminate_due_to_signal at emacs.c:362
handle_fatal_signal at sysdep.c:1628
deliver_thread_signal at sysdep.c:1602
deliver_fatal_thread_signal at sysdep.c:1640
?? at crt1.c:0
??
??:0
??
??:0
??
??:0

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16511 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#16511: 24.3.50; emacs_backtrace.txt
Date: Tue, 21 Jan 2014 05:47:49 +0200

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Tue, 21 Jan 2014 03:56:18 +0100
> Cc: 16511 <at> debbugs.gnu.org
> 
> ??
> ??:0
> mark_object at alloc.c:5955
> ??
> ??:0
> ??
> ??:0
> w32_backtrace at w32fns.c:8383
> emacs_abort at w32fns.c:8415
> terminate_due_to_signal at emacs.c:378
> die at alloc.c:6761
> make_natnum at lisp.h:736
> Flength at fns.c:110
> concat at fns.c:515
> Fcopy_sequence at fns.c:447
> 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:5566
> shut_down_emacs at emacs.c:2017
> terminate_due_to_signal at emacs.c:362
> handle_fatal_signal at sysdep.c:1628
> deliver_thread_signal at sysdep.c:1602
> deliver_fatal_thread_signal at sysdep.c:1640

Another crash in GC.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Juanma Barranquero <lekktu <at> gmail.com>, 16511 <at> debbugs.gnu.org,
 drew.adams <at> oracle.com
Subject: Re: bug#16511: 24.3.50; emacs_backtrace.txt
Date: Sun, 09 Feb 2014 19:48:31 -0800

Eli Zaretskii <eliz <at> gnu.org> writes:

>> shut_down_emacs at emacs.c:2017
>> terminate_due_to_signal at emacs.c:362
>> handle_fatal_signal at sysdep.c:1628
>> deliver_thread_signal at sysdep.c:1602
>> deliver_fatal_thread_signal at sysdep.c:1640
>
> Another crash in GC.

Should these be kept open, or is no possible progress to be made?

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

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: lekktu <at> gmail.com, 16511-done <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#16511: 24.3.50; emacs_backtrace.txt
Date: Mon, 10 Feb 2014 17:57:31 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: Juanma Barranquero <lekktu <at> gmail.com>,  16511 <at> debbugs.gnu.org,  drew.adams <at> oracle.com
> Date: Sun, 09 Feb 2014 19:48:31 -0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> shut_down_emacs at emacs.c:2017
> >> terminate_due_to_signal at emacs.c:362
> >> handle_fatal_signal at sysdep.c:1628
> >> deliver_thread_signal at sysdep.c:1602
> >> deliver_fatal_thread_signal at sysdep.c:1640
> >
> > Another crash in GC.
> 
> Should these be kept open, or is no possible progress to be made?

Since no one is looking at these GC problems, I don't see a reason to
keep this one open.

Previous Next

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