From: Eli Zaretskii <eliz@gnu.org>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v4 - part 0/4)
Date: Fri, 14 Nov 2008 22:58:00 -0000 [thread overview]
Message-ID: <uej1eno8t.fsf@gnu.org> (raw)
In-Reply-To: <BC96B060-6D1C-4B2B-B5A0-70348185823F@adacore.com>
> From: Tristan Gingold <gingold@adacore.com>
> Date: Fri, 14 Nov 2008 17:26:23 +0100
>
> here is a new version (v4) of the Darwin/x86 port.
> I think I have addressed all comments:
Thanks.
> *** gdb/NEWS 22 Oct 2008 22:14:21 -0000 1.292
> --- gdb/NEWS 14 Nov 2008 16:17:20 -0000
> ***************
> *** 169,174 ****
> --- 169,178 ----
> These allow macros to be defined, undefined, and listed
> interactively.
>
> + * New native configurations
> +
> + x86 Darwin i[34567]86-*-darwin*
> +
This is okay, but I thought you also support x86_64?
> 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.
> + @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.
> + 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?
next prev parent reply other threads:[~2008-11-14 18:43 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 [this message]
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
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=uej1eno8t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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