public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan at vrany dot io" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30249] upgrade the GDB to 13.1 version, hookpost-extended-remote will not work.
Date: Wed, 29 Mar 2023 13:17:39 +0000 [thread overview]
Message-ID: <bug-30249-4717-eR8Rte11zE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30249-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30249
Jan Vrany <jan at vrany dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan at vrany dot io
--- Comment #1 from Jan Vrany <jan at vrany dot io> ---
I can reproduce the bug and created a tentative fix, see
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f48f80529710f7dc9a87c6821315b7a1fa66853e
I'll run it through my CI and eventually submit.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-29 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 8:57 [Bug gdb/30249] New: " wenyan.xin at windriver dot com
2023-03-20 8:59 ` [Bug gdb/30249] " wenyan.xin at windriver dot com
2023-03-20 8:59 ` wenyan.xin at windriver dot com
2023-03-29 13:17 ` jan at vrany dot io [this message]
2023-05-19 12:38 ` cvs-commit at gcc dot gnu.org
2023-05-20 0:27 ` tromey at sourceware dot org
2023-05-20 0:27 ` tromey at sourceware dot org
2023-05-20 7:06 ` [Bug gdb/30249] [13 regression] " sam at gentoo dot org
2023-05-20 19:45 ` cvs-commit at gcc dot gnu.org
2023-05-20 19:50 ` jan at vrany dot io
2023-05-24 18:48 ` tromey 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-30249-4717-eR8Rte11zE@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).