Subject: Re: bug#17602: 24.4.50; emacs_backtrace.txt

From: Eli Zaretskii <[email-masked]>
Date: Mon, 26 May 2014 22:18:54 +0300

> Date: Mon, 26 May 2014 22:15:42 +0300
> From: Eli Zaretskii <[email-masked]>
> Cc: [email-masked]
> 
> > From: Juanma Barranquero <[email-masked]>
> > Date: Mon, 26 May 2014 20:48:32 +0200
> > Cc: [email-masked]
> > 
> > ??
> > ??:0
> > w32_backtrace at w32fns.c:8478
> > emacs_abort at w32fns.c:8510
> > terminate_due_to_signal at emacs.c:382
> > die at alloc.c:6955
> > cleanup_vector at alloc.c:2963
> > sweep_vectors at alloc.c:3003
> > gc_sweep at alloc.c:6773
> > Fgarbage_collect at alloc.c:5680
> > maybe_gc at lisp.h:4522
> > Ffuncall at eval.c:2766
> > call3 at eval.c:2645
> > cmd_error_internal at keyboard.c:1085
> > cmd_error at keyboard.c:1054
> > internal_condition_case at eval.c:1351
> > command_loop_2 at keyboard.c:1177
> > internal_catch at eval.c:1118
> > command_loop at keyboard.c:1156
> > recursive_edit_1 at keyboard.c:777
> > Frecursive_edit at keyboard.c:848
> 
> Another duplicate of 16414.

Btw, note that this happens when Emacs wants to report an error.