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 #92 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: Fri, 19 Mar 2021 11:14:40 -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: Fri, 19 Mar 2021 10:21:18 -0400
>> 
>> Lisp Backtrace:
>> "kill-buffer" (0xfffeca60)
>> 0x56e58d70 PVEC_COMPILED
>> "substitute-command-keys" (0xfffed728)
>> "redisplay_internal (C function)" (0x0)
>
> Thanks.  This case isn't interesting, because this is a temporary
> buffer we don't display.  So I guess we need to augment the breakpoint
> condition:
>
>   break buffer.c:1840 if redisplaying_p != 0 && b->window_count > 0

Okay.  I'll run with that for a while and see if I can't trigger the
crash (or breakpoint) again.

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




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

Previous Next


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