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: Re: Cleanup varobj children handling
Date: Mon, 18 Dec 2006 07:28:00 -0000	[thread overview]
Message-ID: <em5fue$l0d$1@sea.gmane.org> (raw)
In-Reply-To: <elchh7$5i1$1@sea.gmane.org>

Vladimir Prus wrote:

> Vladimir Prus wrote:
> 
>> 
>> This patch changes varobj.c to use VEC for hodling children, thereby
>> making three functions unnecessary. No regressions in MI tests. OK?
> 
> I forgot to remove some more dead code -- struct varobj_child is no longer
> needed. This patch removes it too.
> 
> - Volodya
> 
>         gdb/
>         * varobj.c: Include "vec.h".
>         (varobj_p): New typedef, declare vector of those.
>         (struct varobj): Use vector for the 'children' member.
>         (child_exists): Remove.
>         (save_child_in_parent): Remove.
>         (remove_child_from_parent): Remove.
>         (struct varobj_child): Remove.
>         (varobj_list_children): Adjust to work work vector.
>         (varobj_update): Likewise.
>         (delete_variable_1): Likewise.
>         * Makefile.in (varobj.o): Update dependencies.
> 
>         testsuite/
>         * gdb.mi/mi-var-child.exp: Adjust to the change in order
>         of varobjs reported by -var-update.
>         * gdb.mi/mi2-var-child.exp: Likewise.

PING? The above was posted 10 days ago.

- Volodya





  reply	other threads:[~2006-12-18  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 20:00 Vladimir Prus
2006-12-08 20:22 ` Vladimir Prus
2006-12-18  7:28   ` Vladimir Prus [this message]
2006-12-21 15:25 ` Vladimir Prus
2006-12-21 22:42   ` Nick Roberts
2006-12-22  6:18     ` Vladimir Prus
2006-12-22  6:49       ` Nick Roberts
2006-12-22  7:26         ` Vladimir Prus
2006-12-26 16:10   ` Daniel Jacobowitz
2006-12-26 20:50     ` Vladimir Prus
2006-12-30 14:57       ` Daniel Jacobowitz

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='em5fue$l0d$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