* bug#16511: 24.3.50; emacs_backtrace.txt
@ 2014-01-21 0:18 Drew Adams
2014-01-21 2:56 ` Juanma Barranquero
0 siblings, 1 reply; 5+ messages in thread
From: Drew Adams @ 2014-01-21 0:18 UTC (permalink / raw)
To: 16511
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@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'
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#16511: 24.3.50; emacs_backtrace.txt
2014-01-21 0:18 bug#16511: 24.3.50; emacs_backtrace.txt Drew Adams
@ 2014-01-21 2:56 ` Juanma Barranquero
2014-01-21 3:47 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Juanma Barranquero @ 2014-01-21 2:56 UTC (permalink / raw)
To: Drew Adams; +Cc: 16511
??
??: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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#16511: 24.3.50; emacs_backtrace.txt
2014-01-21 2:56 ` Juanma Barranquero
@ 2014-01-21 3:47 ` Eli Zaretskii
2014-02-10 3:48 ` Lars Ingebrigtsen
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2014-01-21 3:47 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: 16511
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 21 Jan 2014 03:56:18 +0100
> Cc: 16511@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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#16511: 24.3.50; emacs_backtrace.txt
2014-01-21 3:47 ` Eli Zaretskii
@ 2014-02-10 3:48 ` Lars Ingebrigtsen
2014-02-10 15:57 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Lars Ingebrigtsen @ 2014-02-10 3:48 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: Juanma Barranquero, 16511
Eli Zaretskii <eliz@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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#16511: 24.3.50; emacs_backtrace.txt
2014-02-10 3:48 ` Lars Ingebrigtsen
@ 2014-02-10 15:57 ` Eli Zaretskii
0 siblings, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2014-02-10 15:57 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: lekktu, 16511-done
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Juanma Barranquero <lekktu@gmail.com>, 16511@debbugs.gnu.org, drew.adams@oracle.com
> Date: Sun, 09 Feb 2014 19:48:31 -0800
>
> Eli Zaretskii <eliz@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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-02-10 15:57 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-21 0:18 bug#16511: 24.3.50; emacs_backtrace.txt Drew Adams
2014-01-21 2:56 ` Juanma Barranquero
2014-01-21 3:47 ` Eli Zaretskii
2014-02-10 3:48 ` Lars Ingebrigtsen
2014-02-10 15:57 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).