From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Doug Evans <dje@google.com>, Vladimir Prus <ghost@cs.msu.su>,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] Variable objects for STL containers
Date: Tue, 26 Feb 2008 02:34:00 -0000 [thread overview]
Message-ID: <20080226023059.GC4456@caradoc.them.org> (raw)
In-Reply-To: <18360.46269.11283.751538@kahikatea.snap.net.nz>
On Mon, Feb 18, 2008 at 11:27:08AM +1300, Nick Roberts wrote:
> This is not any STL, but Gcc's STL. Gdb and Gcc are both part of the GNU
> project so should possibly have a special relationship.
I agree, but I don't think this is the way to do it. I've found that
the easier we make it to hack on this sort of thing (in this case,
support for custom display of objects), the more likely we are to get
people who are experienced in the right areas to help out. Suppose we
support this as a bunch of text scripts, ignoring what language
they're written in. Then they can ship with GDB for old versions of
GCC but transition to shipping with GCC for new versions of libstdc++;
and I think the libstdc++ maintainers will be happy to improve them
and keep them up to date.
> I don't really understand how the python support will be implemented but I
> don't see why variable objects for STL containers should require Python
> libraries to be present.
Script engines are just tools. If we want to use tools, I think it's
OK to have a dependence on them. For practical reasons, I believe we
should use generally portable tools and (for now, at least) support
building a functional GDB without them; that's the decision we made
for expat.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-26 2:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 3:33 Nick Roberts
2008-02-15 14:29 ` Marc Khouzam
2008-02-15 14:42 ` Daniel Jacobowitz
2008-02-15 21:57 ` Nick Roberts
2008-02-17 13:36 ` Vladimir Prus
2008-02-17 20:18 ` Nick Roberts
2008-02-17 21:57 ` Doug Evans
2008-02-17 22:27 ` Nick Roberts
2008-02-26 2:34 ` Daniel Jacobowitz [this message]
2008-02-18 7:45 ` 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=20080226023059.GC4456@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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