From: Roger Phillips <heidegg@hotmail.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Tom de Vries <tdevries@suse.de>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Adding a condition on a hardware watchpoint based on watchpoint state
Date: Fri, 1 Sep 2023 19:57:22 +0000 [thread overview]
Message-ID: <PH0PR06MB8652504AC9E606A3B9B9BBFBAAE4A@PH0PR06MB8652.namprd06.prod.outlook.com> (raw)
In-Reply-To: <ebeeccadc97c9c8beb9e3432b6c09d9f43652002.camel@skynet.be>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
Thanks will try!
________________________________
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Sent: Friday, September 1, 2023 7:00 PM
To: Roger Phillips <heidegg@hotmail.com>; Tom de Vries <tdevries@suse.de>; gdb@sourceware.org <gdb@sourceware.org>
Subject: Re: Adding a condition on a hardware watchpoint based on watchpoint state
In the meantime, you should be able to do what you want with command attached to the
watch point such as the below that watches the value of a variable i.
watch -location i
set var $prev = i
command $bpnum
if $prev < i
printf "increase prev %d %d \n", $prev, i
set var $prev = i
else
printf "decrease prev %d %d \n", $prev, i
set var $prev = i
continue
end
end
On Tue, 2023-08-29 at 11:55 +0000, Roger Phillips via Gdb wrote:
> Very well, thank you. Can you imagine if and when this goes into a release?
>
> Regards
>
> ________________________________
> From: Tom de Vries <tdevries@suse.de>
> Sent: Tuesday, August 29, 2023 10:24 AM
> To: Roger Phillips <heidegg@hotmail.com>; gdb@sourceware.org <gdb@sourceware.org>
> Subject: Re: Adding a condition on a hardware watchpoint based on watchpoint state
>
> On 8/28/23 13:41, Roger Phillips via Gdb wrote:
> > Greetings,
> >
> > I want to install a condition on a hardware watchpoint so that only accesses are stopped that increase the value of the variable 1 -> 2 etc.
> >
> > Is this possible?
> >
>
> There's an enhancement PR open about this (
> https://sourceware.org/bugzilla/show_bug.cgi?id=29480 ).
>
> Thanks,
> - Tom
>
prev parent reply other threads:[~2023-09-01 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 11:41 Roger Phillips
2023-08-29 10:24 ` Tom de Vries
2023-08-29 11:55 ` Roger Phillips
2023-09-01 19:00 ` Philippe Waroquiers
2023-09-01 19:57 ` Roger Phillips [this message]
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=PH0PR06MB8652504AC9E606A3B9B9BBFBAAE4A@PH0PR06MB8652.namprd06.prod.outlook.com \
--to=heidegg@hotmail.com \
--cc=gdb@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=tdevries@suse.de \
/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).