Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: LRN <lrn1986@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Sun, 30 Sep 2012 07:51:00 -0000	[thread overview]
Message-ID: <83ipawdk3n.fsf@gnu.org> (raw)
In-Reply-To: <50674CCF.9020800@gmail.com>

> Date: Sat, 29 Sep 2012 23:32:31 +0400
> From: LRN <lrn1986@gmail.com>
> 
> > First, please use "MS-Windows" instead of "W32".
> OK, although it might not be technically correct. I have no idea
> whether ReactOS implements this debugging facility or not, but if it
> does, then it is not right to name it "MS-Windows", since ReactOS is
> neither MS, nor Windows.
> I usually use "W32", because most of the time doing something with
> WinAPI means interacting with Win32 subsystem, which, as i've
> mentioned above, [is not/will not be] implemented exclusively by Windows.
> Now, since GNU folks frown upon "win" in Win32, and naming it Woe32
> sounds weird to me, i just use "W32".

W32 is not an acronym known to users.  We can use "Windows API", if
you think this is more accurate.

> +@kindex signal-event
> +@item signal-event @var{id}
> +This command signals an event with user-provided @var{id}. Used to resume
                                                            ^^

Please use 2 spaces between sentences.

> +To use it, create or edit the following keys in
> +@code{HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug} and/or
> +@code{HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug}
> +(for x86_64 versions):
> +
> +@itemize @minus
> +@item
> +Debugger (REG_SZ)

"Debugger" should be in @code{}.

>  - a command to launch the debugger. Suggested command is:
   ^

Three dashes here, "---", so that in print there will be a nice
em-dash character.  One dash is typeset as a minus sign, not what you
wanted.

> +<fully-qualified-path-to-gdb.exe> -ex "attach %ld" -ex "signal-event %ld"
> +-ex "c"

The command should be in @code, and it should use @var for something
the user should substitute.  Like this:

 Suggested command: @code{@var{absolute-file-name-of-gdb.exe} -ex
 "attach %ld" -ex "signal-event %ld" -ex "continue"}.

> +First %ld will be replaced by process ID, second %ld will be replaced by ID
> +of the event that blocks the crashing process, waiting for debugger to attach.

Please put the %ld in @code{}.

> +@item
> +Auto (REG_SZ) - either @code{1} or @code{0}. @code{1} will make the system run

"Auto" should be in @code{}.

> +debugger specified by Debugger key automatically, @code{0} will cause a dialog
> +box with "OK" and "Cancel" buttons to appear, which allows the user to either
> +terminate crashing process (OK) or debug it (Cancel).

Please use ``OK'' and ``Cancel'', not double quotes, for better looks
in print.

The documentation patch is OK with those changes.

Thanks.


  reply	other threads:[~2012-09-30  7:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 17:55 LRN
2012-08-31 14:53 ` Eli Zaretskii
2012-08-31 15:37   ` LRN
2012-09-10  2:22     ` LRN
2012-09-10 18:15       ` Tom Tromey
2012-09-10 18:32         ` LRN
2012-09-11 18:21       ` Pedro Alves
2012-09-11 18:27         ` LRN
2012-09-11 18:30           ` Pedro Alves
2012-09-11 18:09     ` Pedro Alves
2012-09-11 18:23       ` LRN
2012-09-11 18:27         ` Pedro Alves
2012-09-11 18:31           ` LRN
2012-09-29 12:42           ` LRN
2012-09-29 13:05             ` Eli Zaretskii
2012-09-29 19:32               ` LRN
2012-09-30  7:51                 ` Eli Zaretskii [this message]
2012-09-30 12:46                   ` LRN
2012-10-01 13:18                     ` Eli Zaretskii
2012-10-01 16:22                       ` LRN
2012-08-31 15:37   ` Christopher Faylor
2012-08-31 15:40     ` LRN
2012-10-01 22:37 ` Sergio Durigan Junior
2012-10-01 22:48   ` LRN
2012-10-02  5:53     ` Sergio Durigan Junior
2012-10-02 12:48       ` Joel Brobecker
2012-10-02 12:57         ` LRN
2016-06-30 13:17           ` LRN
2016-06-30 15:25             ` Eli Zaretskii
2016-06-30 15:44               ` LRN
2016-06-30 16:23                 ` Eli Zaretskii
2016-06-30 17:19                   ` LRN
2016-06-30 17:42                     ` Eli Zaretskii
2016-06-30 18:36                       ` LRN
2016-06-30 18:57                         ` Eli Zaretskii
2016-06-30 19:14                           ` LRN
2016-07-02  1:16                             ` LRN
2016-07-02  7:48                               ` Eli Zaretskii
2016-07-10 13:06                                 ` LRN
2016-07-10 14:55                                   ` Eli Zaretskii
2016-07-18 10:08                                     ` LRN
2016-07-19 19:10                                       ` Eli Zaretskii
2016-07-20  4:43                                         ` LRN
2016-07-23  8:41                                           ` Eli Zaretskii

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=83ipawdk3n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lrn1986@gmail.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