bug#81544: 32.0.50; abort in Finsert_file_contents probably at yank-ing

andrei.elkin--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <[email protected]> Mon, 03 Aug 2026 20:08:36 +0300
Newsgroups gmane.emacs.bugs
Organization Home sweet home
Message-ID <871pcfi12j.fsf@quad>
Howdy Eli!

>> Date: Mon, 03 Aug 2026 16:40:08 +0300
>> From: Andrei Elkin via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <[email protected]>
>> 
>> I got a crash while attempting to yank a killed line.
>> I can't remember exactly but the mouse select might also have taken
>> place right before the line killing.
>> 
>> In the following please find bt, xbacktrace and bt full.
>> A gdb session is alive for those who would dare to investigate.
>
> Thanks.  It seems you show two different crashes here?

I am sorry, I picked some old stacks, inadvertently.

The intended stack is on L35875

Thread 1 "emacs" received signal SIGABRT, Aborted.                                        
__pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at pthread_ki\
ll.c:44                                                                                   
warning: 44     pthread_kill.c: No such file or directory                                 
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at pthrea\
d_kill.c:44                                                                               
#1  __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78      
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at pthread_kill.c\
:89                                                                                       
#3  0x00007ffff384527e in __GI_raise (sig=6) at raise.c:26                                
#4  0x000055555578c87b in terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at \
emacs.c:480                                                                               
#5  0x00005555558477ee in die (msg=0x555555a20a55 "val == true", file=0x555555a1f8f8 "tre\
esit.c", line=4240) at alloc.c:7353                                                       
#6  0x000055555595ec60 in treesit_assume_true (val=false) at treesit.c:4240               
#7  0x000055555595ee5c in treesit_cursor_helper_1 (cursor=0x7fffffff3ec0, target=0x7fffff\
ff3e60, start_pos=4430, end_pos=4430, limit=1) at treesit.c:4287                          
#8  0x000055555595edb7 in treesit_cursor_helper_1 (cursor=0x7fffffff3ec0, target=0x7fffff\
ff3e60, start_pos=4430, end_pos=4430, limit=2) at treesit.c:4276                          
...

it mentions treesitter (I believe I have more stacks with it,
unreported, to compare with the current one).


>
> Anyway, the second one is due to a known bug in treesit.c, which was
> fixed 1 day after you updated from Git.  So please update again and
> rebuild.

Let's hope on that!

>
> Not sure what the first crash is about, but it sounds like Magit
> triggers some kind of auto-revert, and that hits an assertion in
> insert-file-contents.

That one is irrelevant.

Thank you!

/ndrei