Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Darwin/x86 port (v4 - part 0/4)
Date: Mon, 17 Nov 2008 21:03:00 -0000	[thread overview]
Message-ID: <E5336D72-AB56-4C43-8DD4-644FE7FABC70@adacore.com> (raw)
In-Reply-To: <uej1eno8t.fsf@gnu.org>


On Nov 14, 2008, at 7:42 PM, Eli Zaretskii wrote:
>> *** gdb/NEWS	22 Oct 2008 22:14:21 -0000	1.292
>> + * New native configurations
>> +
>> + x86 Darwin			i[34567]86-*-darwin*
>> +
>
> This is okay, but I thought you also support x86_64?

Right.  What about:

* New native configurations

x86/x86_64 Darwin		i[34567]86-*-darwin*


I realized that we don't support configuring as x86_64-*-darwin*.   
Maybe I should
add it ?

>>  The bigger the value is the more verbose the output is.
>
> Suggest to rephrase:
>
>  "Higher values produce more verbose output."
>
> If you agree, please make this change in all the other places you use
> a similar phrase.

Sure.  English is not my native language and I sometimes don't pick  
the right word.

>> + @item set debug mach-o @var{num}
>> + @kindex set debug mach-o
>> + 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
>
> Do all Darwin developers know what is "mach-o object file processing"?
> If not, perhaps a sentence or two of explanations are due.

Ok.

>> +                 If on any inferior faults (but single stepping and
>> + breakpoint) will be reported as a mach exception before being  
>> reported to
>> + the kernel.
>
> "If on, any inferior faults (except single stepping and breakpoint
>  traps) will be announced as mach exceptions before being reported to
>  the kernel."
>
> To tell the truth, I don't really understand the meaning of the
> mach-exceptions option, nor when it will be useful to GDB users.  Can
> you explain?

I tried to explain better in the documentation.  Basically it is  
useful to understand the
reason of why a signal was sent.

Here is the updated doc patch.

Thank you for your comments,
Tristan.


+ @node Darwin
+ @subsection Darwin
+ @cindex Darwin
+
+ @value{GDBN} provides the following commands specific to the Darwin  
target:
+
+ @table @code
+ @item set debug darwin @var{num}
+ @kindex set debug darwin
+ When set to a non zero value, enables debugging messages specific to
+ the Darwin support.  Higher values produce more verbose output.
+
+ @item show debug darwin
+ @kindex show debug darwin
+ Show the current state of Darwin messages.
+
+ @item set debug mach-o @var{num}
+ @kindex set debug mach-o
+ 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.  Higher values produce more verbose
+ output.
+
+ @item show debug mach-o
+ @kindex show debug mach-o
+ Show the current state of mach-o file messages.
+
+ @item set mach-exceptions on
+ @itemx set mach-exceptions off
+ @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.
+
+ @item show mach-exceptions
+ @kindex show mach-exceptions
+ Show the current state of exceptions trapping.
+ @end table
+


  reply	other threads:[~2008-11-17  9:39 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 [this message]
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

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=E5336D72-AB56-4C43-8DD4-644FE7FABC70@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