bug#31245: 27.0.50; Crash in Windows emacs

[Andy Moreton <andrewjmoreton@gmail.com>]

On Mon 23 Apr 2018, Eli Zaretskii wrote:

>> From: Andy Moreton <andrewjmoreton@gmail.com>
>> Date: Mon, 23 Apr 2018 14:51:34 +0100
>> 
>> I am seeing occasional crashes in emacs, but am currently unable to
>> run gdb on my machine at $work.
>> 
>> Decoding emacs_backtrace.txt gives:
>> 
>> w32_backtrace at C:/emacs/git/emacs/master/src/w32fns.c:10645
>> emacs_abort at C:/emacs/git/emacs/master/src/w32fns.c:10680
>> bidi_pop_it at C:/emacs/git/emacs/master/src/bidi.c:946
>> pop_it at C:/emacs/git/emacs/master/src/xdisp.c:6265
>> next_overlay_string at C:/emacs/git/emacs/master/src/xdisp.c:5662
>> set_iterator_to_next at C:/emacs/git/emacs/master/src/xdisp.c:7779
>> move_it_in_display_line_to at C:/emacs/git/emacs/master/src/xdisp.c:9230
>> move_it_to at C:/emacs/git/emacs/master/src/xdisp.c:9480
>> partial_line_height at C:/emacs/git/emacs/master/src/xdisp.c:10047
>> try_window at C:/emacs/git/emacs/master/src/xdisp.c:17759
>> redisplay_window at C:/emacs/git/emacs/master/src/xdisp.c:17181
>
> Thanks, but this kind of problems is impossible to debug without a
> reproducer.  Can you come up with one?

Sure, but it will take some time as this only happens every few days.

> Also, do all the crashes you see show the same backtrace?

As yet unknown, as the backtrace is always written to the same file, so
the old ones have been overwritten.

    AndyM