Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: muller@cerbere.u-strasbg.fr
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC 2nd ver] New info command for win32 native target
Date: Mon, 18 Feb 2002 11:32:00 -0000	[thread overview]
Message-ID: <2947-Mon18Feb2002212931+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <4.2.0.58.20020218143531.013a7fa8@ics.u-strasbg.fr> (message from Pierre Muller on Mon, 18 Feb 2002 14:59:37 +0100)

> Date: Mon, 18 Feb 2002 14:59:37 +0100
> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
> 
> After the remarks from Eli and Christopher, I 
> change my patch to try to complete their requests.

Thanks!

> +@node Win32 Native

I suggest "Windows" instead of "Win32".  Some people, including some
that belong to The Powers That Be, don't like calling Windows ``a
win'', and we don't want to rewrite large portions of the manual
every time they look at our documentation ;-)

> +@cindex @sc{Win32} debugging

It's not recommended to use @sc on a string that involves both lower-
and upper-case letters.

> +@item info w32 selector
> +This command displays information returned by
> +the Win32 API GetThreadSelectorEntry function.

The string "GetThreadSelectorEntry" is a name of a function, so it
should be in @code.

> +@item new-group
> +This boolean value controls whether the debuggee should
> +start a new group or stay in the same group as the debugger.
> +This affects the handling of certain Win32 exceptions.

I think this description should be expanded a bit (what exceptions?
affects how?).


  reply	other threads:[~2002-02-18 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06  2:23 [RFC] " Pierre Muller
2002-02-06  3:24 ` Eli Zaretskii
2002-02-06  3:58   ` Pierre Muller
2002-02-06  4:27     ` Eli Zaretskii
2002-02-06 10:00   ` Christopher Faylor
2002-02-18  6:01   ` [RFC 2nd ver] " Pierre Muller
2002-02-18 11:32     ` Eli Zaretskii [this message]
2002-02-18 19:59       ` Christopher Faylor
2002-02-19  0:57         ` Pierre Muller

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=2947-Mon18Feb2002212931+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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