GNU bug report logs - #16968
24.3.50; emacs_backtrace.txt

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16968 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#16968: 24.3.50; emacs_backtrace.txt
Date: Sat, 08 Mar 2014 20:00:26 +0200

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Sat, 8 Mar 2014 18:50:45 +0100
> Cc: 16968 <at> debbugs.gnu.org
> 
> w32_backtrace at w32fns.c:8431
> emacs_abort at w32fns.c:8463
> terminate_due_to_signal at emacs.c:378
> die at alloc.c:6775
> check_glyph_memory at dispnew.c:2223
> shut_down_emacs at emacs.c:2041
> Fkill_emacs at emacs.c:1952
> Ffuncall at eval.c:2815
> exec_byte_code at bytecode.c:919
> funcall_lambda at eval.c:2983
> Ffuncall at eval.c:2864
> exec_byte_code at bytecode.c:919
> funcall_lambda at eval.c:2983
> Ffuncall at eval.c:2864
> Fcall_interactively at callint.c:836
> Ffuncall at eval.c:2822
> exec_byte_code at bytecode.c:919
> funcall_lambda at eval.c:2983
> Ffuncall at eval.c:2864
> call1 at eval.c:2614
> command_loop_1 at keyboard.c:1556
> internal_condition_case at eval.c:1354
> command_loop_2 at keyboard.c:1174
> internal_catch at eval.c:1118
> command_loop at keyboard.c:1145
> recursive_edit_1 at keyboard.c:777
> Frecursive_edit at keyboard.c:845
> Ffuncall at eval.c:2812
> exec_byte_code at bytecode.c:919
> funcall_lambda at eval.c:2983
> Ffuncall at eval.c:2864
> Fapply at eval.c:2354
> apply1 at eval.c:2588
> call_debugger at eval.c:332
> maybe_call_debugger at eval.c:1733
> Fsignal at eval.c:1551
> xsignal at eval.c:1588
> xsignal2 at eval.c:1609
> eval_sub at eval.c:2130

This says that Emacs signaled an error, which invoked the debugger,
and then Emacs was shut down without exiting the debugger.

Drew, any idea what caused the shutdown?

Previous Next

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