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


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Welsh Duggan <mwd <at> cert.org>
Cc: mwd <at> md5i.com, 47244 <at> debbugs.gnu.org, schwab <at> linux-m68k.org
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Mon, 29 Mar 2021 18:27:31 +0300
> 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?

> `g` calls the following function:
> 
>     (defun gnus-server-exit ()
>       "Return to the group buffer."
>       (interactive nil gnus-server-mode)
>       (gnus-run-hooks 'gnus-server-exit-hook)
>       (gnus-kill-buffer (current-buffer))

What is current-buffer at this point?




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.