From: Tristan Gingold <gingold@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v4 - part 0/4)
Date: Wed, 19 Nov 2008 20:44:00 -0000 [thread overview]
Message-ID: <4EC45EDD-771D-4793-BBDA-2695CFF08275@adacore.com> (raw)
In-Reply-To: <49221D88.1000500@codesourcery.com>
Hi Stan,
thank you for the reviewing. I have made the changes, the testsuite
is now running.
I will post the new diffs soon.
I am replying to all the mail at least to double check I didn't forget
anything.
Tristan.
On Nov 18, 2008, at 2:42 AM, Stan Shebs wrote:
> Tristan Gingold wrote:
>> + @item set debug inferior @var{num}
> We're changing this from "inferior" to "darwin", right?
Right.
>> + When set to a non zero value, enables debugging messages specific
>> to mach-o
>> + object file processing. The bigger the value is the more verbose
>> the
>> + output is.
> Capitalize "Mach-O" here. Also add a comment to the effect that this
> is mainly to diagnose problems internal to GDB, and should not be
> needed in normal usage.
Done.
> With these changes, the bits here are OK for the trunk (and I'll be
> the first person to try them out once checked in!).
Thank you for your interest!
prev parent reply other threads:[~2008-11-19 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:14 Tristan Gingold
2008-11-14 18:50 ` Pedro Alves
2008-11-14 18:51 ` Tristan Gingold
2008-11-14 21:05 ` Stan Shebs
2008-11-14 22:07 ` Pedro Alves
2008-11-17 19:36 ` Daniel Jacobowitz
2008-11-17 21:55 ` Tristan Gingold
2008-11-14 22:58 ` Eli Zaretskii
2008-11-17 21:03 ` Tristan Gingold
2008-11-18 3:35 ` Eli Zaretskii
2008-11-19 23:03 ` Tristan Gingold
2008-11-18 17:46 ` Stan Shebs
2008-11-19 20:44 ` 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=4EC45EDD-771D-4793-BBDA-2695CFF08275@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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