Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] varobj.c memory leaks
Date: Thu, 08 Nov 2001 08:10:00 -0000	[thread overview]
Message-ID: <3BFA8F11.9DB324B8@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0111200900271.19213-100000@makita.cygnus.com>

Keith Seitz wrote:
> 
> Hi,
> 
> I was looking at c++ problems in varobj when I noticed that we had a few
> memory leaks.
> 
> *_name_of_child allocates memory for the return result. The result must be
> xfreed when no longer needed.
> 
> I've tested this on gdb.mi/mi-var-display.exp, gdb.mi/mi-watch.exp,
> gdb.gdbtk/c_variable.exp, and gdb.gdbtk/cpp_variable.exp, and it has no
> regressions.
> 
> Keith
> 

Thanks.  Please check it in.

F.


> ChangeLog
> 2001-11-20  Keith Seitz  <keiths@redhat.com>
> 
>         * varobj.c (c_value_of_child): Release memory for "name" when
>         finshed using it.
>         (c_type_of_child): Likewise.
>         (cplus_value_of_child): Isolate the use of name_of_child to
>         one case that needs it.
>         Release memory for "name" when finished using it.
> 
> Patch
> Index: varobj.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/varobj.c,v
> retrieving revision 1.24
> diff -u -p -r1.24 varobj.c
> --- varobj.c    2001/11/19 19:44:04     1.24
> +++ varobj.c    2001/11/20 17:03:27
> @@ -1977,6 +1977,7 @@ c_value_of_child (struct varobj *parent,
>    if (value != NULL)
>      release_value (value);
> 
> +  xfree (name);
>    return value;
>  }
> 
> @@ -2019,6 +2020,7 @@ c_type_of_child (struct varobj *parent,
>        break;
>      }
> 
> +  xfree (name);
>    return type;
>  }
> 
> @@ -2281,7 +2283,6 @@ cplus_value_of_child (struct varobj *par
>  {
>    struct type *type;
>    struct value *value;
> -  char *name;
> 
>    if (CPLUS_FAKE_CHILD (parent))
>      type = get_type_deref (parent->parent);
> @@ -2289,19 +2290,22 @@ cplus_value_of_child (struct varobj *par
>      type = get_type_deref (parent);
> 
>    value = NULL;
> -  name = name_of_child (parent, index);
> 
>    if (((TYPE_CODE (type)) == TYPE_CODE_STRUCT) ||
>        ((TYPE_CODE (type)) == TYPE_CODE_UNION))
>      {
>        if (CPLUS_FAKE_CHILD (parent))
>         {
> +         char *name;
>           struct value *temp = parent->parent->value;
> 
> +         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))
>         {

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2001-11-20 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  6:33 Keith Seitz
2001-11-08  8:10 ` Fernando Nasser [this message]
2001-11-08  8:59   ` Keith Seitz

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=3BFA8F11.9DB324B8@redhat.com \
    --to=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@cygnus.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