From: "Andrew Burgess" <aburgess@broadcom.com>
To: "Pedro Alves" <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] hardware watchpoints turned off, inferior not yet started
Date: Fri, 18 Oct 2013 15:43:00 -0000 [thread overview]
Message-ID: <5261572A.1090701@broadcom.com> (raw)
In-Reply-To: <52615305.3050909@redhat.com>
On 18/10/2013 4:25 PM, Pedro Alves wrote:
> On 10/18/2013 10:14 AM, Andrew Burgess wrote:
>> After my patch then we do indeed see the error earlier, when the second
>> "file foo" is issued.
>
> BTW, not super important, but thinking out loud, I think it'd
> make sense to have the "set can-use-hw-watchpoints" command
> itself trigger a breakpoint/watchpoint reset.
I initially planned to do just this, but the manual says that after
a "set can-use-hw-breakpoints 0" previous breakpoints will remain
hardware while future ones will be software.
This clearly breaks a little (depending on interpretation) with
restarting the inferior / changing the file but we'd either need
to update the manual or carry additional information around on the
watchpoint to indicate if it's supposed to be HW/SW.
Thanks for taking the time to review my patch :)
Andrew
next prev parent reply other threads:[~2013-10-18 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 9:39 Andrew Burgess
2013-10-16 12:32 ` Pedro Alves
2013-10-16 15:43 ` Andrew Burgess
2013-10-16 16:28 ` Pedro Alves
2013-10-18 9:14 ` Andrew Burgess
2013-10-18 14:37 ` Andrew Burgess
2013-10-18 15:33 ` Pedro Alves
2013-10-18 16:26 ` Andrew Burgess
2013-10-18 15:26 ` Pedro Alves
2013-10-18 15:43 ` Andrew Burgess [this message]
2013-11-07 12:21 Jose E. Marchesi
2013-11-08 12:03 ` Pedro Alves
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=5261572A.1090701@broadcom.com \
--to=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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