Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Watchpoint single-stepping.
Date: Mon, 09 Oct 2006 18:09:00 -0000	[thread overview]
Message-ID: <1160417337.14535.27.camel@localhost.localdomain> (raw)
In-Reply-To: <baf6008d0610081301o646a6585i8d733d5a190c37f3@mail.gmail.com>

On Sun, 2006-10-08 at 21:01 +0100, Rob Quill wrote:
> 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.

This is a tall order.  Even to attempt to explain how gdb works 
in this area would be a big effort.  I suggest that, if you want
to do something that works kind of like a watchpoint, you spend
some time figuring out how watchpoints work.  Set a watchpoint, 
then step thru the gdb code to figure out how it works.  Concentrate
on infrun.c and breakpoint.c.

Take lots of notes.  ;-)

> On a side note, does GDB maintain a internal model of the control flow
> graph of the program being executed.

No.  Nothing even remotely similar.



      reply	other threads:[~2006-10-09 18:09 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
2006-10-09 18:09       ` Michael Snyder [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=1160417337.14535.27.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    --cc=rob.quill@gmail.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