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: Thu, 08 Apr 2021 19:35:19 +0300

> From: Michael Welsh Duggan <mwd <at> cert.org>
> Date: Thu, 08 Apr 2021 12:01:23 -0400
> Cc: Michael Welsh Duggan <mwd <at> md5i.com>,
>  "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>,
>  "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>
> 
> Lisp Backtrace:
> "window-list-1" (0xffffbfa0)
> "replace-buffer-in-windows" (0xffffc4a8)
> "kill-buffer" (0xffffc710)
> 0x571d80f8 PVEC_COMPILED
> "substitute-command-keys" (0xffffd3d8)
> "command-error-default-function" (0xffffd628)
> "apply" (0xffffd7e8)
> 0xf2c1d0e8 PVEC_COMPILED

This seems to indicate that kill-buffer is called by
substitute-command-keys, in which case the buffer in question is a
temporary buffer.  Can you verify that by looking at the buffer's name
in frame #13:

> #13 0x0000555555758e6d in Fkill_buffer (buffer_or_name=XIL(0x5555571d7ced)) at ../../master/src/buffer.c:1830
>         buffer = XIL(0x5555571d7ced)
>         b = 0x5555571d7ce8
>         tem = XIL(0x555555753673)
>         m = 0x7fffffffc5f0

And if I'm right, it sounds like we are looking at a different
scenario here?  The previous calls to kill-buffer were from Gnus,
right?

Previous Next

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