Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 29 Sep 2012 16:42:03 +0400
> From: LRN <lrn1986@gmail.com>
> 
> +@kindex signal-event
> +@item signal-event @var{id}
> +This command signals an event with user-provided @var{id}. Used to resume crashing
> +process when attached to it using W32 JIT debugging (AeDebug).

First, please use "MS-Windows" instead of "W32".

More importantly, I think we should document the Registry entry the
user needs to tweak, and how to define it, in order to install GDB as
a JIT debugger.  In other words, the above does not explain enough
about the expected use of this command, which (AFAIU) is from the GDB
command line using the -ex switch, which I understand is the only way
to get hold of the mysterious ID parameter this command needs.

> +  c = add_com ("signal-event", class_run, signal_event_command,
> +	       _("Signal an object with ID."));

This, too, is too vague to be useful.  After you show the full
description for the manual of how to use this command, I can help you
making its short variant for the documentation string of the command.

Thanks.