Subject: bug#16234: 24.3.50; emacs_backtrace.txt

From: Eli Zaretskii <[email-masked]>
Date: Tue, 24 Dec 2013 19:56:29 +0200

> From: Juanma Barranquero <[email-masked]>
> Date: Tue, 24 Dec 2013 05:39:37 +0100
> Cc: [email-masked]
> 
> ??
> ??:0
> find_interval at intervals.c:679
> ??
> ??:0
> ??
> ??:0
> w32_backtrace at w32fns.c:8385
> emacs_abort at w32fns.c:8417
> terminate_due_to_signal at emacs.c:378
> handle_fatal_signal at sysdep.c:1628
> deliver_thread_signal at sysdep.c:1602
> deliver_fatal_thread_signal at sysdep.c:1640

Aha! the trap worked!  I installed in trunk revision something that
will hopefully show us a full backtrace from intervals.c:679, so we
could try to find out whodunit.

Thanks.