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

Previous Next

Full log

View this message in rfc822 format

From: Michael Welsh Duggan <mwd <at> cert.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: Michael Welsh Duggan <mwd <at> md5i.com>, martin rudalics <rudalics <at> gmx.at>, "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>, "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Thu, 08 Apr 2021 09:39:03 -0400

Gregory Heytings <gregory <at> heytings.org> writes:

>>> I have no suggestion, but a question: why don't you try to bisect this 
>>> bug?
>>
>> Probably because this bug sits just around the corner - we are only not 
>> able to see it.  Bisecting is problematic for two reasons: It takes 
>> Michael some time to reproduce the bug and it's not yet clear whether 
>> the functionality of an older Emacs would allow him to reproduce that 
>> bug in the first place.
>>
>
> I see, but still, given the time you've already spent on this, would it 
> not be easier to check whether say HEAD~2000 already has the bug?  IIUC 
> the reproduction is always under the same condition: resetting Gnus after 
> switching the VPN.

Unfortunately, although it always triggers under the same condition, it
doesn't trigger every time I'm in that condition.  In fact, I don't know
that I've every been able to trigger it more than twice in a day, even
when manually attempting to create the circumstances that might do so.
And some days I haven't been able to trigger it at all.

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

Previous Next

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