From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Anirban Sinha <ASinha@zeugmasystems.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: [gdb-7.0] One week to the gdb-7.0 release!
Date: Wed, 30 Sep 2009 16:20:00 -0000 [thread overview]
Message-ID: <20090930162038.GA7190@bromo.med.uc.edu> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C501FD7F8F@exchange.ZeugmaSystems.local>
On Tue, Sep 29, 2009 at 05:44:18PM -0700, Anirban Sinha wrote:
> >We've had some last-second instability on the branch, which we should
> >now have taken care of. Unless we find some evidence of the contrary,
> >we're now thinking that it would be more prudent to extend the testing
> >period for a few more days, probably until Monday or Tuesday next week.
>
> Sigh ...
I haven't tested the gdb 7.0 branch yet, but gdb trunk seems to be
totally broken now on darwin even with the proposed patch...
http://sourceware.org/ml/gdb-patches/2009-09/msg00430.html
Now gdb errors out earlier and claims that darwin executables
aren't valid executable files. Is anyone else seeing that on
darwin?
Jack
ps This is from './dist/bin/gdb ./a.out'.
next prev parent reply other threads:[~2009-09-30 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 22:09 Joel Brobecker
2009-09-29 23:17 ` Anirban Sinha
2009-09-30 0:13 ` Joel Brobecker
2009-09-30 0:44 ` Anirban Sinha
2009-09-30 16:20 ` Jack Howarth [this message]
2009-09-30 16:30 ` Joel Brobecker
2009-09-30 16:59 ` Jack Howarth
2009-09-30 17:08 ` Paul Pluzhnikov
2009-09-30 17:31 ` Jack Howarth
2009-09-30 17:42 ` Paul Pluzhnikov
2009-09-30 17:45 ` Jack Howarth
2009-09-30 17:34 ` Joel Brobecker
2009-10-01 11:29 ` gdb seems to be broken on darwin 10.5.8 and later Jonas Maebe
2009-10-02 1:53 ` Jack Howarth
2009-10-02 15:40 ` Joel Brobecker
2009-10-02 16:12 ` Jack Howarth
2009-10-02 16:20 ` 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=20090930162038.GA7190@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=ASinha@zeugmasystems.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