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

Le vendredi 23 mai 2008 à 18:43 +0400, Vladimir Prus a écrit :

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

I do, my plugin can handle this kind of STL type imbrication.

> > 
> > 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?
> 

3.5.1

indeed, it seems there is a problem with KDevelop

If you try a very simple project like that :

#include <vector>

int main(int, char **)
{
	std::vector<int> v;
	v.push_back(1);
	v.push_back(2);
	v.push_back(3);
	v.push_back(4);
	v[2]=5;
	*(v.begin()) = 6;
	return 0;
}

	in KDevelop, place a breakpoint on the "v.push_back(2);" line, add a
watch expression to 'v'.

	Expand local and watch views of 'v' variable. Then step line by line,
and you'll see that 'watch' part is correctly updated, whereas 'local'
part is not.

	Could it be fixed by something in my GDB patch, or is it a KDevelop
problem, ie does KDevelop assumes that an array never changes its size ?



  reply	other threads:[~2008-05-23 16:32 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
2008-05-23 20:39       ` Vincent Benony [this message]
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=1211560307.6621.26.camel@bsr-desktop \
    --to=vbenony@nordnet.fr \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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