From: "Rob Quill" <rob.quill@gmail.com>
To: gdb@sourceware.org
Subject: Re: Watchpoint single-stepping.
Date: Sun, 08 Oct 2006 20:01:00 -0000 [thread overview]
Message-ID: <baf6008d0610081301o646a6585i8d733d5a190c37f3@mail.gmail.com> (raw)
In-Reply-To: <baf6008d0610081301k49a5bff5ueed19f1c5f60e6ab@mail.gmail.com>
Hi,
Thanks for your help. What I am trying to do is mimic the way a
software watchpoint works, in that I want to make GDB single-step
through the program and then compare the values of the current
variables to some other values. What suggestions would you have for
implementing this, as I'm not sure how to go about it becasue there is
no documentation in GDB Internals on how single-stepping is done.
On a side note, does GDB maintain a internal model of the control flow
graph of the program being executed.
Thanks for your help.
Rob
On 08/10/06, Frédéric Riss <frederic.riss@gmail.com> wrote:
> Le samedi 07 octobre 2006 à 23:55 +0100, Rob Quill a écrit :
> > I am trying to find the point in the code where the conditions of a
> > software watchpoint are checked each step, as I wish to add something
> > that also requires the checking of values of variables at each step.
> > Does anyone know where this is?
>
> All the low-level stepping is done in the infrun.c file. Look
> particularly at the handle_inferior_event function which is called for
> each target stop event. There you'll find calls to bpstat_stop_status
> (defined in breakpoint.c) where watchpoint expressions are re-evealuated
> and compared to their old value.
>
> Fred.
>
>
next prev parent reply other threads:[~2006-10-08 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 22:55 Rob Quill
2006-10-07 23:13 ` Frédéric Riss
[not found] ` <1160262732.5142.8.camel@funkylaptop>
[not found] ` <baf6008d0610081301k49a5bff5ueed19f1c5f60e6ab@mail.gmail.com>
2006-10-08 20:01 ` Rob Quill [this message]
2006-10-09 18:09 ` Michael Snyder
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=baf6008d0610081301o646a6585i8d733d5a190c37f3@mail.gmail.com \
--to=rob.quill@gmail.com \
--cc=gdb@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