public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows
Date: Wed, 23 Aug 2023 17:50:58 +0000	[thread overview]
Message-ID: <bug-30774-4717-4NRcjkFAzJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30774-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED
   Target Milestone|---                         |13.1

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Valerii Koval from comment #2)

> That's true, the issue is only reproducible with GDB 12. Although it's sad
> to hear that there won't be any bug fix releases in the v12 branch as there
> are plenty of projects like ESP-IDF that uses GDB 12 as their main package.

Yeah, I understand.  And, as a project, gdb is sometimes amenable
to backports of fixes to release branches, even in cases like this
where the branch is closed.  However, that requires someone to
dig up the patch, backport it, show it is harmless and/or doesn't
depend on other patches, etc...

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

  parent reply	other threads:[~2023-08-23 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  9:56 [Bug remote/30774] New: " valeros08 at gmail dot com
2023-08-18 10:31 ` [Bug remote/30774] " ssbssa at sourceware dot org
2023-08-18 13:47 ` tromey at sourceware dot org
2023-08-23  9:24 ` valeros08 at gmail dot com
2023-08-23 17:50 ` tromey at sourceware dot org [this message]
2023-08-23 17:55 ` ssbssa at sourceware 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-30774-4717-4NRcjkFAzJ@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).