public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28616] GDB doesn't rollback displaced stepping state after a failure to insert hardware watchpoints
Date: Sun, 13 Feb 2022 14:08:19 +0000	[thread overview]
Message-ID: <bug-28616-4717-B5zEFSlGwl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28616-4717@http.sourceware.org/bugzilla/>

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

Joel Brobecker <brobecker at gnat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brobecker at gnat dot com

--- Comment #1 from Joel Brobecker <brobecker at gnat dot com> ---
Hi Luis,

IIUC, I think you set the target milestone for this PR to 12.1. As a
side-effect, this is taken as indicating this bug needs to be fixed before we
can release GDB 12. Was that your intention, and if yes, can you provide more
details why?

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

  reply	other threads:[~2022-02-13 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 15:49 [Bug gdb/28616] New: " luis.machado at linaro dot org
2022-02-13 14:08 ` brobecker at gnat dot com [this message]
2022-03-07 11:42 ` [Bug gdb/28616] " brobecker at gnat dot com
2022-03-07 12:00 ` luis.machado at arm dot com
2022-03-07 12:02 ` luis.machado at arm dot com
2022-03-07 12:03 ` luis.machado at arm dot com
2023-05-31  9:47 ` luis.machado at arm dot com

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-28616-4717-B5zEFSlGwl@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).