From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: tromey@redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: Discussing the next GDB release (GDB 7.0?)
Date: Wed, 28 Jan 2009 03:49:00 -0000 [thread overview]
Message-ID: <1233114539.16553.32.camel@localhost.localdomain> (raw)
In-Reply-To: <m363kglcas.fsf@fleche.redhat.com>
El jue, 15-01-2009 a las 10:16 -0700, Tom Tromey escribió:
> As a "stretch" goal we could consider support for new commands and
> parameters implemented in Python, or convenience functions. I think
> that code is also reasonably mature, useful, and independent from the
> other Python bits.
I'd like to see those in as well. My concern is that supporting creation
of new commands and functions without exposing useful bits of GDB to
Python would be of limited usefulness... That's why I was thinking of
submitting other patches first like frames, symbols, blocks etc (though
I concede they may need some reshaping or polishing first).
To start small, submitting a patch for frame support and convenience
functions would already allow implementation of $caller_is... What do
you think?
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-01-28 3:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 3:46 Joel Brobecker
2009-01-15 4:18 ` Eli Zaretskii
2009-01-15 10:43 ` Vladimir Prus
2009-01-15 17:12 ` Joel Brobecker
2009-01-15 17:17 ` Tom Tromey
2009-01-15 17:24 ` Daniel Jacobowitz
2009-01-15 17:31 ` Joel Brobecker
2009-01-28 3:49 ` Thiago Jung Bauermann [this message]
2009-01-30 0:43 ` Joel Brobecker
2009-02-02 13:48 ` Thiago Jung Bauermann
2009-02-04 19:17 ` Tom Tromey
2009-02-06 0:48 ` Joel Brobecker
2009-01-15 17:24 ` David Daney
2009-01-15 17:37 ` Joel Brobecker
2009-01-15 23:54 ` teawater
2009-01-16 2:29 ` teawater
2009-01-16 3:40 ` Joel Brobecker
2009-01-16 6:32 ` teawater
2009-01-16 16:24 ` Tom Tromey
2009-01-16 14:30 ` Marc Khouzam
2009-01-20 18:25 ` Jakob Engblom
2009-01-21 0:18 ` teawater
2009-01-21 3:16 ` teawater
2009-01-27 5:09 ` Michael Snyder
2009-01-27 5:01 ` Michael Snyder
2009-01-30 0:48 ` Joel Brobecker
2009-01-16 3:47 ` Joel Brobecker
2009-01-16 5:48 ` Paul Pluzhnikov
2009-01-16 8:46 ` Eli Zaretskii
2009-01-16 14:55 ` Daniel Jacobowitz
2009-01-16 14:30 ` Joel Sherrill
2009-01-17 3:09 ` Joel Brobecker
2009-01-20 8:09 ` Nathan Sidwell
2009-01-20 10:41 ` Joel Brobecker
2009-01-20 11:25 ` Nathan Sidwell
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=1233114539.16553.32.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tromey@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