From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: time to start thinking about GDB 7.3 (as well!)
Date: Mon, 07 Mar 2011 11:43:00 -0000 [thread overview]
Message-ID: <201103071130.06889.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTikYbr0L4ftvy5z1A6d=MfNtSSr-CCyds08iquLY@mail.gmail.com>
On Monday 07 March 2011 11:18:03, Mike Frysinger wrote:
> On Mon, Feb 14, 2011 at 3:14 PM, Mike Frysinger wrote:
> > On Monday, February 14, 2011 09:50:10 Joel Brobecker wrote:
> >> We should also discuss features that we think would be worthwhile
> >> waiting for. Some Python work being finished, for instance, which
> >> might nicely complements some of the new enhancements we got?
> >> Tracepoints? gdbserver work? Etc.
> >
> > i'd like to the Blackfin sim port merged before the 7.3 branch. i'm not
> > expecting a comprehensive review or anything since the port is so large
> > (==comprehensive). the only thing it needs is an approval ...
>
> well my stuff is in now :), and the wiki page in question is blank ...
Let me put some stuff there then. :-)
Joel, do I still have time to get my second and third parts
of the <unavailable> values support (posted the other week) into 7.3?
<http://sourceware.org/ml/gdb-patches/2011-02/msg00581.html>
<http://sourceware.org/ml/gdb-patches/2011-02/msg00611.html>
WDYT? This makes the tracing experience much better compared to 7.2.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-07 11:30 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
2011-02-14 20:15 ` Mike Frysinger
2011-03-07 11:27 ` Mike Frysinger
2011-03-07 11:43 ` Pedro Alves [this message]
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=201103071130.06889.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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