From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to start thinking about GDB 7.3 (as well!)
Date: Mon, 14 Feb 2011 19:33:00 -0000 [thread overview]
Message-ID: <m3y65ie7lf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110214145010.GX2384@adacore.com> (Joel Brobecker's message of "Mon, 14 Feb 2011 18:50:10 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> According to the tentative calendar, it's also time to start
Joel> thinking about the GDB 7.3 release process. Normally, we were
Joel> planning on branching next week.
Joel> We should also discuss features that we think would be worthwhile
Joel> waiting for. Some Python work being finished, for instance, which
Joel> might nicely complements some of the new enhancements we got?
Joel> Tracepoints? gdbserver work? Etc.
I think Phil is planning to resubmit his Python breakpoint changes this
week.
Jan said on irc that the ifunc branch might be close to merge-ready.
This is important because, without it, `strcmp' is not usable (on
systems with a glibc that uses ifunc) in a breakpoint condition --
pretty basic stuff.
Sergio and I have been working on exposing SystemTap static probe points
to gdb. We are reasonably close to finishing this; the basic
functionality is fine, and this week Sergio is working on the probe
arguments while I work on tests. So, assuming others are amenable to
this idea, we would like this to be in 7.3. I am not sure whether all
the details will be acceptable in the right timeframe; I could post the
"bad" parts if people want to take a look now.
For 7.2.1, I think Jan and Keith have been discussing the C++ regressions.
I'm not sure what they have decided, I'm a little behind on that again.
Tom
next prev parent reply other threads:[~2011-02-14 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 14:52 Joel Brobecker
2011-02-14 19:33 ` Tom Tromey [this message]
2011-02-14 20:15 ` Mike Frysinger
2011-03-07 11:27 ` Mike Frysinger
2011-03-07 11:43 ` Pedro Alves
2011-03-07 12:35 ` Joel Brobecker
2011-03-07 15:44 ` Pedro Alves
2011-02-15 4:06 ` Hui Zhu
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=m3y65ie7lf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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