From: Vladimir Prus <ghost@cs.msu.su>
To: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [mi] kill release_value calls
Date: Wed, 24 Jan 2007 19:55:00 -0000 [thread overview]
Message-ID: <E1H9oDI-0007Pj-6z@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <20070124194009.GA23437@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Daniel Jacobowitz wrote:
> On Wed, Jan 24, 2007 at 10:33:30PM +0300, Vladimir Prus wrote:
>>
>> This patch removes all calls to release_value in varobj.c, except
>> for one. We only need to call release_value when we're storing
>> a value for indefinite future use, and install_new_value is the
>> only such place. The extra release_value calls either
>> are time-consuming no-ops, or lead to memory leaks,
>> depending on the value type.
>>
>> OK?
>
> OK. My apologies to Nick - I'd told him this was wrong, but I was
> mistaken.
Here's what I've checked in -- I had to adjust the patch
for the changes I've checked to mainline earlier today.
- Volodya
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: release_value_as_committed.diff --]
[-- Type: text/x-diff; name="release_value_as_committed.diff", Size: 1754 bytes --]
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.8137
diff -u -p -r1.8137 ChangeLog
--- ChangeLog 24 Jan 2007 13:37:05 -0000 1.8137
+++ ChangeLog 24 Jan 2007 19:53:01 -0000
@@ -1,3 +1,8 @@
+2007-01-24 Vladimir Prus <vladimir@codesourcery.com>
+
+ * varobj.c (c_value_of_root, c_value_of_child)
+ (cplus_describe_child): Don't call release_value.
+
2007-01-24 Thiemo Seufer <ths@mips.com>
* mips-linux-tdep.c (mips_linux_n64_rt_sigframe): Fix struct
Index: varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.81
diff -u -p -r1.81 varobj.c
--- varobj.c 24 Jan 2007 11:08:47 -0000 1.81
+++ varobj.c 24 Jan 2007 19:53:02 -0000
@@ -2020,13 +2020,8 @@ c_value_of_root (struct varobj **var_han
if (within_scope)
{
/* We need to catch errors here, because if evaluate
- expression fails we just want to make val->error = 1 and
- go on */
- if (gdb_evaluate_expression (var->root->exp, &new_val))
- {
- release_value (new_val);
- }
-
+ expression fails we want to just return NULL. */
+ gdb_evaluate_expression (var->root->exp, &new_val);
return new_val;
}
@@ -2038,8 +2033,6 @@ c_value_of_child (struct varobj *parent,
{
struct value *value = NULL;
c_describe_child (parent, index, NULL, &value, NULL);
- if (value != NULL)
- release_value (value);
return value;
}
@@ -2304,7 +2297,6 @@ cplus_describe_child (struct varobj *par
if (cvalue && value)
{
*cvalue = value_cast (TYPE_FIELD_TYPE (type, index), value);
- release_value (*cvalue);
}
if (ctype)
prev parent reply other threads:[~2007-01-24 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 19:33 Vladimir Prus
2007-01-24 19:40 ` Daniel Jacobowitz
2007-01-24 19:55 ` Vladimir Prus [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=E1H9oDI-0007Pj-6z@zigzag.lvk.cs.msu.su \
--to=ghost@cs.msu.su \
--cc=drow@false.org \
--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