public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "igorkuo at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/10136] rwatch not working when set before run
Date: Mon, 13 May 2024 12:28:31 +0000	[thread overview]
Message-ID: <bug-10136-4717-BMSSaiDfWL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10136-4717@http.sourceware.org/bugzilla/>

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

Igor Kushnir <igorkuo at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |igorkuo at gmail dot com

--- Comment #2 from Igor Kushnir <igorkuo at gmail dot com> ---
Cannot reproduce this bug in GDB version 14.2. Tested both the GDB command line
and GDB/MI KDevelop integration. The original (slightly updated) KDevelop test
function GdbTest::testBreakOnReadBreakpoint(), which used to fail and which
Niko Sams disabled in 2009 because of this bug, passes now without the error
message "Target does not support this type of hardware watchpoint.".

Therefore I recommend resolving this bug.

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

       reply	other threads:[~2024-05-13 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10136-4717@http.sourceware.org/bugzilla/>
2024-05-13 12:28 ` igorkuo at gmail dot com [this message]
2024-05-22 17:10 ` tromey at sourceware dot org
2009-05-09 18:55 [Bug breakpoints/10136] New: " niko dot sams at gmail dot com
2009-11-17 22:44 ` [Bug breakpoints/10136] " pedro at codesourcery 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-10136-4717-BMSSaiDfWL@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).