From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.1 release planning...
Date: Mon, 11 Jan 2010 19:58:00 -0000 [thread overview]
Message-ID: <m3hbqsqur7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100109031744.GB27914@adacore.com> (Joel Brobecker's message of "Sat, 9 Jan 2010 07:17:44 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> The filtered backtrace work is not fully baked yet. We know it is still
>> missing some needed features, at least.
Joel> Is this important enough that we want to make it a priority? Do we
Joel> know which pieces need some work.
I'd say it is the second-most-used Python-based feature.
There are a few bug reports about the replacement for "bt" (this written
entirely in Python). It doesn't always do what users need. The details
are in the list archives, I can dig them up if anybody is interested in
working on this.
Also, it doesn't work with MI.
So, while I think it is a worthwhile feature, it needs enough work that
I don't think we should wait for it for 7.1.
Joel> On a side note, what about the Google SoC work? I think it was about
Joel> inferior-events, right? I tried to look at it a few weeks ago, out
Joel> of curiosity, but couldn't find which branch it is a part of? Does
Joel> anyone know? How far are we from being able to submit the code for
Joel> inclusion in the FSF tree? I don't want us to press this feature for
Joel> 7.1, but it'd be nice to not lose all this work. I volunteer to
Joel> clean it up later this year.
I thought it was on a branch in archer, but I don't see it right now.
The author posted a patch series to the archer list. I had a number of
comments, which nobody has addressed yet. So, I think it is promising
but not ready to go in.
Right now most of our Python work is in fixing bugs in pretty printing.
I'd like us to get back to implementing new features, and I think that
will happen sometime, but we have a lot of things going on and so it is
hard to say exactly when.
Tom
next prev parent reply other threads:[~2010-01-11 19:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 4:21 Joel Brobecker
2010-01-08 9:24 ` Tristan Gingold
2010-01-08 11:08 ` Joel Brobecker
2010-01-08 13:49 ` Jan Kratochvil
2010-01-08 18:44 ` Michael Snyder
2010-01-09 3:08 ` Joel Brobecker
2010-01-08 13:53 ` Daniel Jacobowitz
2010-01-08 16:14 ` Tom Tromey
2010-01-09 3:18 ` Joel Brobecker
2010-01-11 19:58 ` Tom Tromey [this message]
2010-01-14 4:54 ` Joel Brobecker
2010-01-08 19:28 ` Stan Shebs
2010-01-08 22:32 ` Pedro Alves
2010-01-08 23:46 ` Stan Shebs
2010-01-09 3:31 ` Joel Brobecker
2010-01-09 16:52 ` Marc Khouzam
2010-01-11 9:48 ` Joel Brobecker
2010-01-11 14:31 ` Pedro Alves
2010-01-11 14:36 ` Pedro Alves
2010-01-13 23:17 ` Michael Snyder
2010-01-14 3:30 ` Joel Brobecker
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=m3hbqsqur7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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