From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Behaviour of invalid varobjs
Date: Sun, 25 Mar 2007 12:03:00 -0000 [thread overview]
Message-ID: <17926.25867.185398.533328@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200703251429.45714.ghost@cs.msu.su>
> The testcase uses "**0", not *0,
Presumably though we're not just interested in the tescase.
> and I don't see any difference between constant and variable below:
>...
> Can you clarify what you meant?
I can't seem to reproduce it now. I must have been mistaken
> > Also, we probably should include in_scope="false" in output of
> > -var-create, but I'm not quite sure.
> >
> > I don't see why.
>
> Because as long as we (IMO, bogusly) use in_scope="false" to indicate
> "expression cannot be evaluated", we should consistently report
> that everywhere.
AFAICS we don't use in_scope at all for -var-create.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-03-25 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 10:40 Vladimir Prus
2007-03-22 10:32 ` Nick Roberts
2007-03-22 10:41 ` Vladimir Prus
2007-03-22 23:53 ` Nick Roberts
2007-03-25 10:30 ` Vladimir Prus
2007-03-25 12:03 ` Nick Roberts [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=17926.25867.185398.533328@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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