From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: [commit][obvious] Remove unused value_object attribute `owned_by_gdb'.
Date: Mon, 30 Mar 2009 03:52:00 -0000 [thread overview]
Message-ID: <1238361753.7100.8.camel@localhost.localdomain> (raw)
Hi,
I just committed this patch.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
Remove unused value_object attribute `owned_by_gdb'.
* python/python-value.c (value_object): Remove owned_by_gdb
attribute.
(valpy_dealloc): Remove reference to self->owned_by_gdb.
(valpy_new): Likewise.
(value_to_value_object): Likewise.
Index: src/gdb/python/python-value.c
===================================================================
--- src.orig/gdb/python/python-value.c 2009-03-29 18:17:43.000000000 -0300
+++ src/gdb/python/python-value.c 2009-03-29 18:17:51.000000000 -0300
@@ -58,7 +58,6 @@ struct value *values_in_python = NULL;
typedef struct {
PyObject_HEAD
struct value *value;
- int owned_by_gdb;
PyObject *address;
} value_object;
@@ -70,8 +69,7 @@ valpy_dealloc (PyObject *obj)
value_remove_from_list (&values_in_python, self->value);
- if (!self->owned_by_gdb)
- value_free (self->value);
+ value_free (self->value);
if (self->address)
/* Use braces to appease gcc warning. *sigh* */
@@ -112,7 +110,6 @@ valpy_new (PyTypeObject *subtype, PyObje
}
value_obj->value = value;
- value_obj->owned_by_gdb = 0;
value_obj->address = NULL;
release_value (value);
value_prepend_to_list (&values_in_python, value);
@@ -746,7 +743,6 @@ value_to_value_object (struct value *val
if (val_obj != NULL)
{
val_obj->value = val;
- val_obj->owned_by_gdb = 0;
val_obj->address = NULL;
release_value (val);
value_prepend_to_list (&values_in_python, val);
reply other threads:[~2009-03-29 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1238361753.7100.8.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
/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