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 19:30:00 -0000 [thread overview]
Message-ID: <g16jrk$3r6$1@ger.gmane.org> (raw)
In-Reply-To: <1211535909.8253.16.camel@bsr-desktop>
Vincent Benony wrote:
> Hello,
>
> some days ago, I send here a (crap and buggy) patch that allows GDB to
> display STL containers. I know that this patch was too intrusive and
> dependent of the STL version.
>
> Today, I wrote another patch that allows me to load plugin into GDB
> that are called in particular situations, like displaying the content of
> a variable of a particular type, or creating varobjects in MI
> interpreter. It is used to format any kind of datas as I want it to be
> displayed.
>
> I submit a new version of my STL container viewer, but this time as a
> plugin. It handles STL container access as it was a classic C array, and
> answers queries like 'sizeof'... It also support MI interpreter, so that
> GDB could be used with frontend, still displaying data correctly. I
> tried it with Eclipse/CDT, KDevelop, KDBG, Nemiver and Insight/GDB. All
> works well !
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
next prev parent reply other threads:[~2008-05-23 14:21 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 [this message]
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
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='g16jrk$3r6$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