GNU bug report logs - #47244
28.0.50; SIGSEGV in long-runnning Emacs

Previous Next

Package: emacs;

Reported by: Michael Welsh Duggan <md5i <at> md5i.com>

Date: Thu, 18 Mar 2021 15:40:01 UTC

Severity: normal

Found in version 28.0.50

Done: Michael Welsh Duggan <mwd <at> md5i.com>

Bug is archived. No further changes may be made.

Full log


Message #461 received at 47244 <at> debbugs.gnu.org (full text, mbox):

From: Michael Welsh Duggan <mwd <at> cert.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "mwd <at> md5i.com" <mwd <at> md5i.com>,
 "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>,
 "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>
Subject: Re: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Thu, 08 Apr 2021 13:51:24 -0400
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Michael Welsh Duggan <mwd <at> cert.org>
>> Cc: Michael Welsh Duggan <mwd <at> md5i.com>,
>>         "schwab <at> linux-m68k.org"
>>  <schwab <at> linux-m68k.org>,
>>         "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>
>> Date: Thu, 08 Apr 2021 13:11:34 -0400
>> 
>> I hit the breakpoint in quit.  It looks like Fnconc uses FOR_EACH_TAIL,
>> which uses FOR_EACH_TAIL_INTENAL, which calls maybe_quit.  The question
>> in my mind now is whether block/unblock_input belongs in window_list or
>> in Fnconc.
>
> IMO, the right solution is not block_input but unwind_protect.

Mayhap.  I look forward to a patch to try out.  (I'm not certain how it
should be used, myself.)

FWIW, it might be worth looking through all uses of FOR_EACH_TAIL to
find places that it is used in loops that do destructive updates, like
Fdelete, as it seems icky for C-g to leave one of these operations
partially completed.

-- 
Michael Welsh Duggan
(mwd <at> cert.org)




This bug report was last modified 4 years and 27 days ago.

Previous Next


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