From: Tristan Gingold <gingold@adacore.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC] Darwin: add OSO as separate debug files
Date: Thu, 14 Jan 2010 12:48:00 -0000 [thread overview]
Message-ID: <25948B80-E662-4BF0-920C-49CA078A70BE@adacore.com> (raw)
In-Reply-To: <0777751C-F4F2-477A-A734-F547889F9ECE@adacore.com>
On Jan 7, 2010, at 10:06 AM, Tristan Gingold wrote:
>
> On Jan 6, 2010, at 8:18 PM, Tom Tromey wrote:
>
>>>>>>> "Tristan" == Tristan Gingold <gingold@ACT-Europe.FR> writes:
>>
>> Tristan> in order to correctly handle Darwin OSO files, they are now added as
>> Tristan> separate debug objfile.
>> Tristan> This is the Darwin specific use of the previous patch.
>>
>> I read through this and didn't see anything obviously objectionable.
>> I don't know anything about Darwin, though, so I think you will have to
>> self-approve.
>
> Thanks.
and committed.
prev parent reply other threads:[~2010-01-14 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:32 Tristan Gingold
2010-01-06 19:19 ` Tom Tromey
2010-01-07 9:05 ` Tristan Gingold
2010-01-14 12:48 ` Tristan Gingold [this message]
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=25948B80-E662-4BF0-920C-49CA078A70BE@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@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