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: 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: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Mon, 29 Mar 2021 11:34:39 -0400

Michael Welsh Duggan <mwd <at> cert.org> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> From: Michael Welsh Duggan <mwd <at> cert.org>
>>> Cc: "mwd <at> md5i.com" <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: Mon, 29 Mar 2021 11:21:05 -0400
>>> 
>>> 2) From the *Group* buffer I hit `C-g` to cancel its attempt, and `^` to
>>>    switch to the Gnus *Sever* buffer.
>>> 3) In that buffer I go to the imap connection and type `C O`, which runs
>>>    `gnus-server-close-server` and `gnus-server-open-server`,
>>>    respectively.
>>> 4) I type `q` to exit the server buffer.  This is when the breakpoint
>>>    triggers.
>>
>> Breakpoint or segfault?
>
> Breakpoint on the `error` clause that Martin asked me to add to
> `set_buffer_internal_2`.

To clarify, this is where the breakpoint triggered this time.  In this
identical scenario in past runs, this is when the segfault happened.

-- 
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.