From: Tristan Gingold <gingold@adacore.com>
To: tromey@redhat.com
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Support multiple separate debug objfiles
Date: Wed, 06 Jan 2010 10:22:00 -0000 [thread overview]
Message-ID: <95ACAF2F-A271-4F07-A7B7-004C2A69E797@adacore.com> (raw)
In-Reply-To: <m3tyv06tk1.fsf@fleche.redhat.com>
On Jan 6, 2010, at 12:06 AM, Tom Tromey wrote:
>>>>>> "Tristan" == Tristan Gingold <gingold@ACT-Europe.FR> writes:
>
> Tristan> I think the best way to support this Darwin particularity is to
> Tristan> extended the notion of separate debug objfiles and allowing
> Tristan> multiple separate debug objfiles.
>
> Seems reasonable.
>
> Tristan> /* Return non-zero if OBJFILE has full or partial symbols, either directly
> Tristan> - or throught its separate debug file. */
> Tristan> + or throught a separate debug file. */
>
> Since you're already modifying this line, would you mind fixing the
> typo? s/throught/through/
>
> This is ok with that change.
Thank you for the review. Committed with this typo fix.
Tristan.
prev parent reply other threads:[~2010-01-06 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:31 Tristan Gingold
2010-01-05 23:06 ` Tom Tromey
2010-01-06 10:22 ` 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=95ACAF2F-A271-4F07-A7B7-004C2A69E797@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
--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