public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/29796] gdbserver should imply --once if connected via stdio
Date: Mon, 26 Aug 2024 14:45:24 +0000	[thread overview]
Message-ID: <bug-29796-4717-duRQ0DtuuG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29796-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29796

--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a733b2c90463231d9fb8b143e168403d96efe54f

commit a733b2c90463231d9fb8b143e168403d96efe54f
Author: William Ferreira <wqferr@gmail.com>
Date:   Thu Jul 18 16:38:31 2024 -0300

    gdb: imply --once if connecting via stdio

    Currently, gdbserver hangs after stdin is closed while it tries to
    write: "Remote side has terminated connection.  GDBserver will reopen
    the connection." This hang disappears if --once is also given. Since
    the stdin connection won't ever reopen if it's closed, it's safe to
    assume --once is desired.

    The gdb.server/server-pipe.exp test was also updated to reflect this
    change. There is now a second disconnect at the end of the proc,
    with a tighter-than-normal timeout to catch if the command hangs as
    it used to.

    Co-Authored-By: Guinevere Larsen <blarsen@redhat.com>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29796

    Approved-By: Andrew Burgess <aburgess@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-08-26 14:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 19:40 [Bug server/29796] New: " pedro at palves dot net
2022-11-16 19:41 ` [Bug server/29796] " simon.marchi at polymtl dot ca
2023-12-29  0:29 ` tromey at sourceware dot org
2024-06-12 13:54 ` tromey at sourceware dot org
2024-06-12 14:37 ` mark at klomp dot org
2024-06-12 14:43 ` mark at klomp dot org
2024-08-26 14:45 ` cvs-commit at gcc dot gnu.org [this message]
2024-08-27 18:18 ` tromey at sourceware dot org
2024-11-16  7:24 ` brobecker at gnat dot com
2024-11-16 14:08 ` mark at klomp dot org

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

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

  git send-email \
    --in-reply-to=bug-29796-4717-duRQ0DtuuG@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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.
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).