This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
- From: Eli Zaretskii <eliz at gnu dot org>
- To: LRN <lrn1986 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 01 Oct 2012 15:18:33 +0200
- Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
- References: <503E575D.1000608@gmail.com> <83y5kvp0za.fsf@gnu.org> <5040DA38.2070802@gmail.com> <504F7E31.10306@redhat.com> <504F818B.6090104@gmail.com> <504F8297.5090507@redhat.com> <5066EC9B.4000409@gmail.com> <838vbtf07z.fsf@gnu.org> <50674CCF.9020800@gmail.com> <83ipawdk3n.fsf@gnu.org> <50683F26.6010004@gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sun, 30 Sep 2012 16:46:30 +0400
> From: LRN <lrn1986@gmail.com>
>
> Attached the patch.
Thanks. Final 2 comments:
. you patch has 2 stray ^M characters, please remove them when
committing
. you still have at least one place with 1 space between sentences
> > The documentation patch is OK with those changes.
> You said you'd suggest a better short message for add_com().
Right, thanks for the reminder. Here it is:
Signal a crashed process with event ID, to allow its debugging.
This command is needed in support of setting up GDB as JIT debugger
on MS-Windows. The command should be invoked from the GDB command
line using the '-ex' command-line option. The ID of the event that
blocks the crashed process will be supplied by the Windows JIT
debugging mechanism.
Well, maybe not so short ;-)
Thanks.