From: Joel Brobecker <brobecker@adacore.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Anirban Sinha <ASinha@zeugmasystems.com>, gdb@sourceware.org
Subject: Re: [gdb-7.0] One week to the gdb-7.0 release!
Date: Wed, 30 Sep 2009 16:30:00 -0000 [thread overview]
Message-ID: <20090930162949.GI5072@adacore.com> (raw)
In-Reply-To: <20090930162038.GA7190@bromo.med.uc.edu>
> 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?
Again, you really have to qualify your statement with which version
of Darwin you are using.
I believe that you are using Snow Leopard whereas things to be OK
on Leopard. The problem on Snow Leopard seems to be coming from
the fact that the method for giving GDB the priviledges it needs
in order to debug the program have changed. AdaCore is planning on
looking at that, eventually, but we just won't have the resources
to do so for at least a few weeks.
--
Joel
next prev parent reply other threads:[~2009-09-30 16:30 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
2009-09-30 16:30 ` Joel Brobecker [this message]
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=20090930162949.GI5072@adacore.com \
--to=brobecker@adacore.com \
--cc=ASinha@zeugmasystems.com \
--cc=gdb@sourceware.org \
--cc=howarth@bromo.med.uc.edu \
/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