Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 7.0: 5 weeks to branch-time...
Date: Thu, 02 Apr 2009 03:26:00 -0000	[thread overview]
Message-ID: <u3acrkaap.fsf@gnu.org> (raw)
In-Reply-To: <20090401215827.GF8930@adacore.com>

> Date: Wed, 1 Apr 2009 14:58:27 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Hello everyone,
> 
> We're getting closer to our desired branch time, so I thought
> a quick update on our situation would be nice. I'm looking at
> our TODO list for this release
> (http://www.sourceware.org/gdb/wiki/GDB_7.0_Release):
> 
>   * Assert in frame.c:get_frame_arch
>     I don't think anyone actually triggered that assert so far, so
>     we might not have to remove it from the branch. We can postpone
>     that decision for after we've created the branch.
> 
>   * Python: Pretty printing
>     Done?
> 
>   * Inlining support
>     Mark to provide some feedback about the proposed patch.
> 
>   * PR/9711: Quadratic slowdown for "where" command. 
>     I don't think anyone worked on that one so far. Any volunteer?
> 
> Optional items:
> 
>   * Python: Support for new parameters and/or convenience functions
>     (?) I forgot what this means :-(
> 
>   * Process record and replay:
>     Sounds like this is still underway
> 
>   * Multiprocess support:
>     Sounds like work is also underway. Status update on how far we are?
> 
> Thanks, everyone. I can't wait to see 7.0 out :).

I still have the issues with file names reported here:

  http://sourceware.org/ml/gdb-patches/2009-03/msg00618.html

I take it that the silence means everyone agrees with the renaming?
If so, I will give it a go in a day or two.


  parent reply	other threads:[~2009-04-02  3:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 21:58 Joel Brobecker
2009-04-01 22:14 ` Tom Tromey
2009-04-02 15:05   ` Thiago Jung Bauermann
2009-04-02 17:31   ` Joel Brobecker
2009-04-02 17:36     ` Tom Tromey
2009-04-02  3:26 ` Eli Zaretskii [this message]
2009-04-02 15:11   ` Daniel Jacobowitz
2009-04-02 19:38     ` Eli Zaretskii
2009-04-03  3:37       ` Daniel Jacobowitz
2009-04-03 11:42         ` Eli Zaretskii
2009-04-02 15:29 ` Thiago Jung Bauermann
2009-04-02 15:40   ` Joel Brobecker
2009-04-02 17:50 ` Pedro Alves

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=u3acrkaap.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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