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, rudalics <at> gmx.at, 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:02:24 +0300

> From: Michael Welsh Duggan <mwd <at> cert.org>
> Cc: "mwd <at> md5i.com" <mwd <at> md5i.com>, "rudalics <at> gmx.at" <rudalics <at> gmx.at>,
>         "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 10:39:35 -0400
> 
> (gdb) p current_buffer->name_
> $4 = XIL(0x5555573519f4)
> (gdb) xstring
> $5 = (struct Lisp_String *) 0x5555573519f0
> " *nntpd*"

Any idea where could be the Lisp code that switches from " *nntpd*" to
the buffer in the currently selected window?  Perhaps some
with-current-buffer thing somewhere?

Since " *nntpd*" is probably a buffer where Gnus fetches articles, or
otherwise communicates with an NNTP server, does this per chance
happen in a separate thread in your session?  (AFAIR, Gnus can fetch
articles in a separate Lisp thread.)

Previous Next

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