bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs

[Michael Welsh Duggan]

martin rudalics <rudalics@gmx.at> writes:

>  >> #0  raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
>  >>          set = {
>  >>            __val = {402653184, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 268435456, 
> 0, 0, 93824994300624, 18446744067266838271}
>  >>          }
>  >>          pid = <optimized out>
>  >>          tid = <optimized out>
>  >> #1  0x00005555557197a1 in terminate_due_to_signal
>  >>      (sig=6, backtrace_limit=2147483647) at ../../master/src/emacs.c:416
>  >> #2  0x00005555557c4858 in die
>  >>      (msg=0x55555594f2a0 "b->window_count == 0", file=0x55555594da8a 
> "../../master/src/buffer.c", line=1969) at ../../master/src/alloc.c:7420
>  >> #3  0x0000555555759190 in Fkill_buffer 
> (buffer_or_name=XIL(0x555557888814))
>  >>      at ../../master/src/buffer.c:1969
>  >>          buffer = XIL(0x555557889325)
>  >>          b = 0x555557889320
>  >>          tem = XIL(0)
>  >>          m = 0x0
>  >
>  > So replace_buffer_in_windows didn't do its job?
>
> Why did replace_buffer_in_windows_safely then apparently fail too?  What
> is the value of b->window_count here?  Unless we managed to botch that's
> buffer's window count, I can't see how replace_buffer_in_windows_safely
> could have possibly failed.

b->window_count is 1.

-- 
Michael Welsh Duggan
(mwd@cert.org)