Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: GDB C plugin system, and STL container viewer as an example
Date: Fri, 23 May 2008 20:31:00 -0000	[thread overview]
Message-ID: <g16l6v$9q6$1@ger.gmane.org> (raw)
In-Reply-To: <1211553158.6621.6.camel@bsr-desktop>

Vincent Benony wrote:

>> I don't see how you report that fact that the number of children of a
>> varobj has changed. Without that, I'm not sure how useful MI display
>> of vectors is. Am I missing something?
>> 
>> - Volodya
> 
> this is done by lines 1157 to 1166 of varobj.c
> 
> 
>       if (plugins_type_handled(varobj_get_gdb_type(*varp)))
>       {
>           int new_childs = plugins_get_num_children(*varp);
>           if (new_childs != (*varp)->num_children)
>           {
>               (*varp)->num_children = new_childs;
>               (*varp)->children = varobj_list_children (*varp);
>               VEC_safe_push (varobj_p, result, *varp);
>           }
>       }
> 
> 
> I evaluate the number of children at each update, and I compare with the
> current number of childs stored in the varobj structure, if different,
> object is added to update list.

What happens for vector< vector<int> >? It does not seem like you handle the
inner items.

> 
> It seems to work well into KDevelop 

Strange, I don't know any codepath in KDevelop 3.5 that could possible handle this.
Which version did you try with?

- Volodya



  reply	other threads:[~2008-05-23 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 18:34 Vincent Benony
2008-05-23 19:30 ` Vladimir Prus
2008-05-23 19:53   ` Daniel Jacobowitz
2008-05-27 18:17     ` Vincent Bénony
2008-05-27 18:21       ` Thiago Jung Bauermann
2008-05-23 19:59   ` Vincent Benony
2008-05-23 20:31     ` Vladimir Prus [this message]
2008-05-23 20:39       ` Vincent Benony
2008-05-23 20:46         ` 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='g16l6v$9q6$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --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