From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10418 invoked by alias); 29 Sep 2012 13:05:48 -0000 Received: (qmail 10409 invoked by uid 22791); 29 Sep 2012 13:05:47 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 29 Sep 2012 13:05:36 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MB400F004BVLW00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Sat, 29 Sep 2012 15:05:34 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MB400FVZ4DALA20@a-mtaout21.012.net.il>; Sat, 29 Sep 2012 15:05:34 +0200 (IST) Date: Sat, 29 Sep 2012 13:05:00 -0000 From: Eli Zaretskii Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32 In-reply-to: <5066EC9B.4000409@gmail.com> To: LRN Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838vbtf07z.fsf@gnu.org> 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> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00703.txt.bz2 > Date: Sat, 29 Sep 2012 16:42:03 +0400 > From: LRN > > +@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.