Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: [mi] kill release_value calls
Date: Wed, 24 Jan 2007 19:33:00 -0000	[thread overview]
Message-ID: <200701242233.30910.ghost@cs.msu.su> (raw)

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]


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?

- Volodya

	* varobj.c (c_value_of_root, c_value_of_child)
	(cplus_value_of_child): Don't call release_value.


[-- Attachment #2: release_value__gdb_mainline.diff --]
[-- Type: text/x-diff, Size: 1380 bytes --]

--- gdb/varobj.c	(/mirrors/gdb_mainline)	(revision 3220)
+++ gdb/varobj.c	(/patches/gdb/release_value/gdb_mainline)	(revision 3220)
@@ -1985,13 +1985,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;
     }
 
@@ -2003,8 +1998,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;
 }
@@ -2338,9 +2331,6 @@ cplus_value_of_child (struct varobj *par
 	  name = name_of_child (parent, index);
 	  gdb_value_struct_elt (NULL, &value, &temp, NULL, name, NULL,
 				"cplus_structure");
-	  if (value != NULL)
-	    release_value (value);
-
 	  xfree (name);
 	}
       else if (index >= TYPE_N_BASECLASSES (type))
@@ -2368,7 +2358,6 @@ cplus_value_of_child (struct varobj *par
 	      if (temp != NULL)
 		{
 		  value = value_cast (TYPE_FIELD_TYPE (type, index), temp);
-		  release_value (value);
 		}
 	      else
 		{

             reply	other threads:[~2007-01-24 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 19:33 Vladimir Prus [this message]
2007-01-24 19:40 ` Daniel Jacobowitz
2007-01-24 19:55   ` 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=200701242233.30910.ghost@cs.msu.su \
    --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