From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Variable objects laziness
Date: Mon, 04 Dec 2006 19:27:00 -0000 [thread overview]
Message-ID: <el1sqf$jvr$1@sea.gmane.org> (raw)
In-Reply-To: <20061128165758.GB21834@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Sat, Nov 18, 2006 at 12:48:05PM +0300, Vladimir Prus wrote:
>> Daniel Jacobowitz wrote:
>>
>> >> + rather value_contents, will take care of this.
>> >> + It might throw, but unlike var-update for -var-assign
>> >> + there's just one variable we're working it, so we don't
>> >> + need to catch the exception here. */
>> >
>> > Wait, what? gdb_value_assign will never throw. value_contents
>> > might, but gdb_value_assign will catch it.
>>
>> Yep, confused gdb_value_assign with value_assign.
>>
>> Updated patch attached. I also attach the delta to the previous patch.
>
> This version is OK now (for HEAD only). Thanks for your patience.
> The frozen varobj patch had some further discussion; I'll have to
> get back to it, but I'm afraid not today. Poke me if I haven't done it
> in a few days, please.
*POKE*.
- Volodya
next prev parent reply other threads:[~2006-12-04 19:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 13:43 Vladimir Prus
2006-11-14 20:47 ` Daniel Jacobowitz
2006-11-15 9:04 ` Vladimir Prus
2006-11-15 16:25 ` Daniel Jacobowitz
2006-11-17 9:23 ` Vladimir Prus
2006-11-17 10:40 ` Mark Kettenis
2006-11-17 10:45 ` Vladimir Prus
2006-11-17 14:22 ` Daniel Jacobowitz
2006-11-17 15:01 ` Vladimir Prus
2006-11-17 17:19 ` Vladimir Prus
2006-11-17 18:12 ` Daniel Jacobowitz
2006-11-18 9:48 ` Vladimir Prus
2006-11-28 17:09 ` Daniel Jacobowitz
2006-12-04 19:27 ` Vladimir Prus [this message]
2006-11-15 2:45 Nick Roberts
2006-11-15 9:22 ` Vladimir Prus
2006-11-29 8:59 Nick Roberts
2006-11-29 2:08 ` Nick Roberts
2006-11-29 2:55 ` Daniel Jacobowitz
2006-11-29 4:14 ` Nick Roberts
2006-11-29 7:25 ` Vladimir Prus
2006-11-29 13:45 ` Daniel Jacobowitz
2006-11-29 13:56 ` Vladimir Prus
2006-11-29 20:25 ` Nick Roberts
2006-11-29 9:09 ` Vladimir Prus
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='el1sqf$jvr$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@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