From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org,
Tristan Gingold <gingold@adacore.com>
Subject: Re: [patch] Fix regression on prelinked executables
Date: Thu, 29 Jul 2010 22:14:00 -0000 [thread overview]
Message-ID: <m3pqy6hr5s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100729213823.GF13267@adacore.com> (Joel Brobecker's message of "Thu, 29 Jul 2010 14:38:23 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> This is fine by me -- but AFAIK Darwin is pretty broken already. At
>> least, there is an open bug with what looks to be a simple crasher.
Joel> I wasn't aware of that. As far as we can tell, it's working fine at
Joel> AdaCore. One of the issues is that neither Tristan nor myself monitor
Joel> the open bugs in bugzilla. If something like this gets reported, I think
Joel> it's work sending Tristan a note.
Ok. I wasn't sure how active he wanted to be with regard to Darwin
bugs.
The one I am thinking of is
http://sourceware.org/bugzilla/show_bug.cgi?id=11488
It looks like some other Darwin bugs may be closeable, just search for
"darwin" in the summary. I see 7, I'd say 5 are probably obsolete --
but that is just guessing.
Joel> Regarding the patch - if a second GM thinks it's safe for 7.2, then
Joel> that's also good enough for me.
I didn't look that closely :)
Tom
next prev parent reply other threads:[~2010-07-29 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 9:55 Jan Kratochvil
2010-07-27 19:22 ` ping: " Jan Kratochvil
2010-07-29 16:37 ` Joel Brobecker
2010-07-29 20:14 ` Tom Tromey
2010-07-29 21:38 ` Joel Brobecker
2010-07-29 22:14 ` Tom Tromey [this message]
2010-07-30 15:45 ` Jan Kratochvil
2010-07-30 15:55 ` Joel Brobecker
2010-07-30 16:06 ` Jan Kratochvil
2010-10-05 20:56 ` [7.2.x-checkin] " Jan Kratochvil
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=m3pqy6hr5s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).