bug#18152: 24.3.92; Crash in emacs 24 while reverting a buffer

[Andy Moreton <andrewjmoreton@gmail.com>]

On 30/07/2014 6:30 PM, Eli Zaretskii wrote:
>> [...]
>> #1  0x011ff2fc in emacs_abort () at ../../src/w32fns.c:8478
>>          button = 0x6
>> #2  0x010f21d6 in terminate_due_to_signal (sig=0x16, backtrace_limit=0x7fffffff) at ../../src/emacs.c:378
>> No locals.
>> #3  0x01164fe0 in die (msg=0x14a0b9a "same_at_start == GPT_BYTE", file=0x14a00a7 "../../src/fileio.c", line=0xfcb) at ../../src/alloc.c:6833
>> No locals.
>> #4  0x0113799a in Finsert_file_contents (filename=0x6364c71, visit=0x37a7842, beg=0x37a7822, end=0x37a7822, replace=0x37a7842) at ../../src/fileio.c:4043
>>          bufpos = 0x38f
>>          this = 0x0
>>          this_count = 0x13
>>          same_at_start = 0x380
>>          same_at_end = 0x390
>>          decoded = 0xb3414b0 "/", '*' <repeats 74 times>, "\\\n*//*! \\file wt_mem.c - WT (Windows Tools) memory allocation helper routines\n** <L5_PRIVATE L5_SOURCE>\n** \\author  al\n**  \\b"...
>
> Unless you can reproduce this at will, it's too bad that you didn't
> record the value of GPT_BYTE, whose difference from same_at_start is
> the immediate reason for the assertion violation on line 4043 of
> fileio.c.

I've seen a couple of crashes in the last week, but only after several hours 
of work. If I manage to reproduce it I will try to keep a gdb session alive to 
aid with debugging.

Regards,

     AndyM