unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 62845@debbugs.gnu.org
Subject: bug#62845: 29.0.90; nntp-with-open-group-function kills current buffer on timeout
Date: Sat, 15 Apr 2023 09:45:20 +0300	[thread overview]
Message-ID: <83pm85ej9b.fsf@gnu.org> (raw)
In-Reply-To: <87a5zauofc.fsf@igel.home> (message from Andreas Schwab on Fri, 14 Apr 2023 23:47:03 +0200)

> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Fri, 14 Apr 2023 23:47:03 +0200
> 
> When the connection to the nntp server times out (if
> nntp-connection-timeout is non-nil) nntp-with-open-group-function kills
> the process buffer.  But that is the current buffer at this point if
> called from nntp-finish-retrieve-group-infos, causing the latter
> function to try to read (and modify!) a random buffer that happend to be
> the LRU buffer at that point.

Thanks.

If this is a recent regression, could you perhaps bisect to find the
offending commit(s)?





  reply	other threads:[~2023-04-15  6:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 21:47 bug#62845: 29.0.90; nntp-with-open-group-function kills current buffer on timeout Andreas Schwab
2023-04-15  6:45 ` Eli Zaretskii [this message]
2023-04-26 23:49   ` Andreas Schwab
2023-04-27  3:08     ` Eric Abrahamsen
2023-05-01 13:19       ` Eli Zaretskii
2023-05-06  0:03         ` Eric Abrahamsen
2023-05-06  3:35           ` Eric Abrahamsen
2023-05-06  5:41             ` Eric Abrahamsen
2023-05-06  6:13               ` Andreas Schwab
2023-05-06 16:58                 ` Eric Abrahamsen
2023-05-06 17:43                   ` Andreas Schwab
2023-05-07  5:52                     ` Eric Abrahamsen
2023-05-07  7:30                       ` Andreas Schwab
2023-05-10 15:53                       ` Eli Zaretskii
2023-05-10 18:21                         ` Eric Abrahamsen
2023-05-11 10:01                           ` Eli Zaretskii
2023-05-11 15:28                             ` Eric Abrahamsen
2023-05-06  6:31           ` Eli Zaretskii
2023-05-06 17:05             ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pm85ej9b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62845@debbugs.gnu.org \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).