From: Peter Barada <peter@baradas.org>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: Multiple locations vs. watchpoints.
Date: Thu, 30 Oct 2003 06:25:00 -0000 [thread overview]
Message-ID: <20031030062538.9FDA29899D@baradas.org> (raw)
In-Reply-To: <20031030055345.GA7588@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 30 Oct 2003 00:53:45 -0500)
>But suppose we have this:
>foo.c:static int *bar;
>bar.c:static int *bar;
>
>(gdb) watch *bar
>
>
>It watches whatever *bar would print, which is one of them. No easy way to
>get at the other or describe the ambiguity. I wonder once again whether the
>two-level scheme is really correctly designed; but I have no better ideas.
You should be able to specify 'watch func::*bar' where func is the name of a
function that has scope on the *bar you are interested in.
I haven't tried this myself, but 'p/x func::foo' is something I've
done too many times to count so reason leads me to believe that the
watch command should use the same evaluator, right?
--
Peter Barada
peter@baradas.org
prev parent reply other threads:[~2003-10-30 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 5:53 Daniel Jacobowitz
2003-10-30 6:21 ` Eli Zaretskii
2003-10-30 19:40 ` Andrew Cagney
2003-10-30 19:44 ` Daniel Jacobowitz
2003-10-30 20:39 ` Eli Zaretskii
2003-10-30 6:25 ` Peter Barada [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=20031030062538.9FDA29899D@baradas.org \
--to=peter@baradas.org \
--cc=drow@mvista.com \
--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