From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Paul Pluzhnikov <ppluzhnikov@google.com>,
Anirban Sinha <ASinha@zeugmasystems.com>,
gdb@sourceware.org, Michael Snyder <msnyder@vmware.com>
Subject: Re: FW: gdb seems to be broken on darwin 10.5.8 and later
Date: Fri, 02 Oct 2009 16:21:00 -0000 [thread overview]
Message-ID: <20091002162146.GB6532@bromo.med.uc.edu> (raw)
In-Reply-To: <m3k4zdss4j.fsf@fleche.redhat.com>
On Fri, Oct 02, 2009 at 10:00:28AM -0600, Tom Tromey wrote:
> >>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>
> >> I am not sure how Joel wants to handle this WRT the 7.0 branch; none
> >> of the other maintainers chimed in :-(
>
> Joel> Did Jack confirm that it does not work without applying your patch?
>
> I read the referenced email. If the only issue with the patch is that
> it is not the best possible way to fix the problem, then I think it
> might as well go in. I say that because I think it generally preferable
> to commit a functioning patch rather than wait for a more ideal patch.
>
> Tom
Tom,
I agree since a functional gdb (even if only as root) will encourage more
folks to work the remaining issues. It also allows darwin users to test gdb
against the new debug support in gcc trunk.
Jack
next prev parent reply other threads:[~2009-10-02 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:37 Anirban Sinha
2009-10-01 3:34 ` Paul Pluzhnikov
2009-10-02 1:55 ` Jack Howarth
2009-10-02 2:13 ` Paul Pluzhnikov
2009-10-02 15:37 ` Joel Brobecker
2009-10-02 16:03 ` Tom Tromey
2009-10-02 16:21 ` Jack Howarth [this message]
2009-10-05 2:57 ` Joel Brobecker
2009-10-05 13:03 ` Jack Howarth
2009-10-05 16:54 ` Joel Brobecker
2009-10-05 22:13 ` Ulrich Weigand
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=20091002162146.GB6532@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=ASinha@zeugmasystems.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=ppluzhnikov@google.com \
--cc=tromey@redhat.com \
/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