From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-56284-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 7507 invoked by alias); 23 May 2008 16:32:14 -0000
Received: (qmail 7491 invoked by uid 22791); 23 May 2008 16:32:10 -0000
X-Spam-Check-By: sourceware.org
Received: from mailman.allo-creation.fr (HELO ns39154.ovh.net) (91.121.20.133)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 23 May 2008 16:31:50 +0000
Received: (qmail 28542 invoked by uid 508); 23 May 2008 16:52:38 -0000
Received: from unknown (HELO ?192.168.1.4?) (82.226.112.216)   by 87-98-251-24.ovh.net with SMTP; 23 May 2008 16:52:38 -0000
Subject: Re: GDB C plugin system, and STL container viewer as an example
From: Vincent Benony <vbenony@nordnet.fr>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
In-Reply-To:  <g16l6v$9q6$1@ger.gmane.org>
References:  <1211535909.8253.16.camel@bsr-desktop> 	 <g16jrk$3r6$1@ger.gmane.org> <1211553158.6621.6.camel@bsr-desktop> 	 <g16l6v$9q6$1@ger.gmane.org>
Content-Type: text/plain; charset=utf-8
Date: Fri, 23 May 2008 20:39:00 -0000
Message-Id: <1211560307.6621.26.camel@bsr-desktop>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-05/txt/msg00685.txt.bz2

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 ?