From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: MI floating varobj of invalid value
Date: Sun, 27 Apr 2008 15:38:00 -0000 [thread overview]
Message-ID: <uiqy4yp1m.fsf@gnu.org> (raw)
Message-ID: <20080427153800.jdVQpgjixayTBhD9usFAd_AfqiRdld1XB5gMP8CLfqo@z> (raw)
In-Reply-To: <200804270127.48885.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sun, 27 Apr 2008 01:27:48 +0400
>
> However, if frontend tries to create varobj for foo
> at the first stop, and 'foo' is not in scope, then varobj will not be created.
Why is that? Since a floating varobj's expression is re-parsed every
time, you should be able to delay parsing and not fail creation
because some of its terms are not in scope, right?
> Does making creation of floating varobj always succeed seem a good idea?
Yes, I think so.
next prev parent reply other threads:[~2008-04-27 5:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:27 Vladimir Prus
2008-04-27 7:51 ` Eli Zaretskii [this message]
2008-04-27 15:38 ` Eli Zaretskii
2008-04-27 21:46 ` Vladimir Prus
2008-04-28 18:02 ` Marc Khouzam
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=uiqy4yp1m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=vladimir@codesourcery.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