From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Tristan Gingold <gingold@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v4 - part 0/4)
Date: Fri, 14 Nov 2008 22:07:00 -0000 [thread overview]
Message-ID: <200811141814.24360.pedro@codesourcery.com> (raw)
In-Reply-To: <491DB997.9090002@codesourcery.com>
On Friday 14 November 2008 17:47:03, Stan Shebs wrote:
> Tristan Gingold wrote:
> >
> > On Nov 14, 2008, at 5:41 PM, Pedro Alves wrote:
> >
> >> On Friday 14 November 2008 16:26:23, Tristan Gingold wrote:
> >>> + @table @code
> >>> + @item set debug inferior @var{num}
> >>> + @kindex set debug inferior
> >>> + When set to a non zero value, enables debugging messages specific to
> >>> + the Darwin support. The bigger the value is the more verbose the
> >>> output is.
> >>
> >> Please don't use "inferior" for darwin specific things. It is a very
> >> general term, and collides with what we may want to do with the
> >> common gdb/inferior.c module.
> >
> > Ok, will change to "maint darwin-debug"
> >
> We have "set debug" that is generally available; some of the options are
> clearly maintenance-only, such as "set debug infrun", so that seems a
> convenient place for a Darwin-specific flag. (We could add "maint set
> debug", but that seems a little too pedantic :-) .)
I'm OK with "set debug", just not "set debug inferior".
"set debug darwin" would also be fine with me.
--
Pedro Alves
next prev parent reply other threads:[~2008-11-14 18:14 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 [this message]
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
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=200811141814.24360.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--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