[Bug,win32/14529] Make gdb capable of JIT-debugging on W32
Commit Message
On 30.06.2016 20:42, Eli Zaretskii wrote:
> On Thu, 30 Jun 2016 20:18:52 +0300, LRN wrote:
>> On 30.06.2016 19:23, Eli Zaretskii wrote:
>>> Thanks, but please format the ChangeLog entries according to our
>>> coding standards. You should be able to see many examples in the
>>> repository.
>>
>> I did. What did i do wrong? Had a single space (instead of two spaces)
>> after the name? Used "Fix PR gdb/14529" at the end instead of "PR
>> gdb/14529" at the beginning? No function name in parentheses (should it
>> have been signal_event_command?)?
>
> The latter.
>
Fixed patches attached.
Comments
> From: LRN <lrn1986@gmail.com>
> Date: Thu, 30 Jun 2016 21:36:12 +0300
>
> >> I did. What did i do wrong? Had a single space (instead of two spaces)
> >> after the name? Used "Fix PR gdb/14529" at the end instead of "PR
> >> gdb/14529" at the beginning? No function name in parentheses (should it
> >> have been signal_event_command?)?
> >
> > The latter.
> >
>
> Fixed patches attached.
Thanks. One last nit is that the ChangeLog entry for gdb.texinfo
should also state a "function name", which is the node name where you
made the changes.
@@ -80,6 +80,12 @@ new-ui INTERP TTY
Start a new user interface instance running INTERP as interpreter,
using the TTY file for input/output.
+signal-event EVENTID
+ Signal ("set") the given Windows event object. This is used together
+ with Windows JIT debugging (AeDebug), where the OS suspends
+ a crashing process until a debugger can attach to it. Resuming
+ the process is done by siganlling an event.
+
* Support for tracepoints and fast tracepoints on s390-linux and s390x-linux
was added in GDBserver, including JIT compiling fast tracepoint's
conditional expression bytecode into native code.