GNU bug report logs - #79318
31.1.90; Threads + receiving a signal causes a segfault

Previous Next

Package: emacs;

Reported by: Spencer Baugh <sbaugh <at> janestreet.com>

Date: Tue, 26 Aug 2025 16:21:02 UTC

Severity: normal

Found in version 31.1.90

Full log


View this message in rfc822 format

From: Spencer Baugh <sbaugh <at> janestreet.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 79318 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>
Subject: bug#79318: 31.1.90; Threads + receiving a signal causes a segfault
Date: Tue, 26 Aug 2025 15:23:20 -0400
Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Tue, 26 Aug 2025 12:19:07 -0400
>> From:  Spencer Baugh via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>> 
>> 
>> repro.el:
>> 
>> (make-thread
>>  (lambda ()
>>    (sleep-for .1)
>>    (signal-process (emacs-pid) 'sigint)))
>> (sleep-for 100)
>> 
>> emacs -Q -l ./repro.el
>> 
>> Observe Emacs crashes with a segfault while shutting down.
>
> I don't see a segfault in your backtrace, only a shutdown due to
> SIGINT (which is a fatal signal in the configuration you ran -- Paul,
> am I right?)

The backtrace is of the point at which there's a segfault.  It happens
during shutdown.

>> In gdb, the segfault appears to be because current_thread is NULL.
>
> Please show the backtrace from the segfault.

I did.




This bug report was last modified 11 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.