public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/10136] rwatch not working when set before run
Date: Tue, 17 Nov 2009 22:44:00 -0000	[thread overview]
Message-ID: <20091117224401.12461.qmail@sourceware.org> (raw)
In-Reply-To: <20090509185516.10136.niko.sams@gmail.com>


------- Additional Comments From pedro at codesourcery dot com  2009-11-17 22:44 -------
This is a consequence of moving watchpoint ops to the target vector, and
to the fact that the native target is only pushed when the inferior is created.

The workaround is running to main before setting the read or access
watchpoints.  E.g. with, '(gdb) start'.

Plain "watch" works, because gdb creates a "software watchpoint" then,
and upgrades it to a hardware watchpoint later, when the process is
actually created (and the native target is pushed on the target stack).


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2009-11-17 22:44 UTC|newest]

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