Subject: Re: bug#15142: 24.3.50; emacs_backtrace.txt

From: Eli Zaretskii <[email-masked]>
Date: Wed, 21 Aug 2013 19:02:19 +0300

> From: Juanma Barranquero <[email-masked]>
> Date: Wed, 21 Aug 2013 01:23:09 +0200
> Cc: [email-masked]
> 
> > Backtrace:
> 
> Fx_popup_dialog at w32menu.c:145
> Fx_popup_dialog at w32menu.c:167
> str_as_multibyte at character.c:652
> allocate_vector_from_block at alloc.c:2723
> expand_and_dir_to_file at fileio.c:1887

I'm beginning to think that the code that produces the backtrace has
some bug, or maybe the crash smashed the stack, because this last part
of the backtrace makes no sense at all.  None of these functions calls
the one above it, certainly not at the lines whose numbers are shown.

> > Backtrace:
> 
> w32_backtrace at w32fns.c:7982
> emacs_abort at w32fns.c:8014
> terminate_due_to_signal at emacs.c:369
> die at alloc.c:6567
> emacs_close at sysdep.c:2272
> close_process_fd at process.c:1630
> deactivate_process at process.c:3847
> remove_process at process.c:765

I believe this was already fixed by Paul recently.