From: Al Niessner <Al.Niessner@jpl.nasa.gov>
To: gdb@sources.redhat.com
Subject: Re: Setting watchpoints
Date: Thu, 17 Apr 2003 20:28:00 -0000 [thread overview]
Message-ID: <1050611295.24877.28.camel@morte.jpl.nasa.gov> (raw)
In-Reply-To: <20030417202008.GB2867@nevyn.them.org>
I am watching a character pointer. 'watch *0x8559ff4' does not work
because that is the value of the pointer in the structure. Watching the
char** instead of char* works great though. To get the char** I did a
print &(symbol->name). So, gdb works as expected and I make mistakes --
as expected?? Thanks for the help though.
On Thu, 2003-04-17 at 13:20, Daniel Jacobowitz wrote:
> On Thu, Apr 17, 2003 at 01:09:59PM -0700, Al Niessner wrote:
> >
> > Platform information:
> > OS: Linux
> > Kernel: 2.4.19
> > gcc/g++: 3.2.2
> > gdb: 5.3
> > threads: 1 -- single threaded application
> >
> >
> > How do I set a watch point so that the debugger halts when memory at a
> > specific address is changed? There is no easy to define variable that I
> > can latch onto, but I do know its address. When I set a watch point to
> > this address -- 'watch 0x8559ff4' or 'watch *0x8559ff4' -- gdb just
> > sails by this memory being changed. If I set a conditional break point
> > just prior to the segmentation fault I can see the change and so can gdb
> > it just does not sense it with the watch. So, what am I doing wrong and
> > how do I get gdb to monitor a memory location and halt when it changes?
> > I have already searched the web (google) and did not find any solutions
> > there.
>
> Does "watch *(int *) 0x8559ff4" work? How big is the area you're
> watching?
--
Al Niessner <Al.Niessner@jpl.nasa.gov>
Jet Propulsion Laboratory
All opinions stated above are mine and do not necessarily reflect those of JPL or NASA.
----
| dS | >= 0
----
prev parent reply other threads:[~2003-04-17 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 20:10 Al Niessner
2003-04-17 20:20 ` Daniel Jacobowitz
2003-04-17 20:28 ` Al Niessner [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=1050611295.24877.28.camel@morte.jpl.nasa.gov \
--to=al.niessner@jpl.nasa.gov \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).