GNU bug report logs -
#47244
28.0.50; SIGSEGV in long-runnning Emacs
Previous Next
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
Message #170 received at 47244 <at> debbugs.gnu.org (full text, mbox):
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:33:02 -0400
>>
>> >> `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?
>>
>> #<buffer *Server*>
>
> I guess this means kill-buffer replaced "*Server*" with " *nntpd*",
> but the selected-window's buffer is still "*Server*", which is being
> killed?
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:33:02 -0400
>>
>> >> `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?
>>
>> #<buffer *Server*>
>
> I guess this means kill-buffer replaced "*Server*" with " *nntpd*",
> but the selected-window's buffer is still "*Server*", which is being
> killed?
No idea. Here's the few places I can see things going wrong, though I
don't know how or why.
kill-buffer calls `replace-buffer-in-windows`, which does a lot of stuff
that I can't account for one way or another.
Hmm... Maybe the `(gnus-configure-windows 'group t)` call is important.
Tracing through it, it's trying to set it to the `group` setting, which
is:
(group
(vertical 1.0
(group 1.0 point)))
This is from `gnus-buffer-configuration`. When I debug
`gnus-all-windows-visible-p` from this `gnus-configure-windows` in a
session that does *not* hit the breakpoint, this function does return
a frame that has the ` *nntpd*` name in its print representation.
But frankly, I'll stick with my original "no idea" statement.
--
Michael Welsh Duggan
(md5i <at> md5i.com)
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.