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

Previous Next

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: Thu, 08 Apr 2021 19:49:53 +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: Thu, 08 Apr 2021 12:37:41 -0400
> 
> >> (gdb) xlist
> >> $16 = 0xb820
> >> Lisp_Symbol
> >> $17 = (struct Lisp_Symbol *) 0x555555e6e8a0 <lispsym+47136>
> >> "quit"
> >> ---
> >> nil
> >
> > So is this the result of your typing C-g?
> 
> Yes.  In the scenario I have presented, this is where Emacs is
> unresponsive (busy cursor), presumably trying to interact with a network
> connection that has gone away to the VPN being switched on or off, and I
> type C-g twice rapidly in succession to regain interactivity, after
> which I would normally then attempt to manually reset the gnus
> connections.

But then the buffer being killed is not the one you reported
originally, is it?  You said the buffer that was killed was *Server*,
and here we see that a temporary buffer is being killed.  Am I
confused?

Previous Next

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