From: Tristan Gingold <gingold@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v4 - part 0/4)
Date: Wed, 19 Nov 2008 23:03:00 -0000 [thread overview]
Message-ID: <D8F661F7-6312-4267-843B-823EB4AF3FBF@adacore.com> (raw)
In-Reply-To: <ud4gum5hu.fsf@gnu.org>
Thank you again for your comments.
>> I realized that we don't support configuring as x86_64-*-darwin*.
>> Maybe I should add it ?
>
> Probably, but I admit I don't know enough about the details.
As this cannot be reported by config.guess, I won't add it now. Could
be of course
revisited later.
>> + When set to a non zero value, enables debugging messages while
>> gdb is
>> + reading Darwin object files. The object and executable file format
>> + for Darwin is named mach-o.
>
> The last sentence above should probably be in parentheses, as that's a
> minor note. Also, I would rearrange slightly:
>
> (@dfn{Mach-o} is the file format used on Darwin for object and
> executable files.)
Ok.
>> + @kindex set mach-exceptions
>> + On Darwin, faults are first reported as a mach exception and then
>> as a
>> + signal. Use this command to turn on trapping of mach exceptions in
>> + the inferior. This might be seldom useful to better understand the
>> + cause of a fault. The default is off.
>
> So you are basically saying that mach exceptions are native Darwin
> exceptions, and they are then mapped to Posix signals? At least that
> is what I understand from this explanation.
Yes. I have used your reworded sentence.
> Also, please make sure you have 2 spaces after each period that ends a
> sentence.
Sure.
Tristan.
next prev parent reply other threads:[~2008-11-19 13:11 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 [this message]
2008-11-18 17:46 ` Stan Shebs
2008-11-19 20:44 ` Tristan Gingold
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=D8F661F7-6312-4267-843B-823EB4AF3FBF@adacore.com \
--to=gingold@adacore.com \
--cc=eliz@gnu.org \
--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