From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24449 invoked by alias); 1 Oct 2009 04:08:37 -0000 Received: (qmail 24440 invoked by uid 22791); 1 Oct 2009 04:08:36 -0000 X-SWARE-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,BAYES_00,BOTNET,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Oct 2009 04:08:31 +0000 Received: from conversion-daemon.i-mtaout1.012.net.il by i-mtaout1.012.net.il (HyperSendmail v2007.08) id <0KQT00L00HOUVU00@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Thu, 01 Oct 2009 06:08:28 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.228.188.180]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KQT0064DI644Z80@i-mtaout1.012.net.il>; Thu, 01 Oct 2009 06:08:28 +0200 (IST) Date: Thu, 01 Oct 2009 04:08:00 -0000 From: Eli Zaretskii Subject: Re: symbolic debug of loadable modules with kgdb light In-reply-to: <5650DA603A804427AA3B3F8F91164548@xpjpn> To: Caz Yokoyama Cc: brobecker@adacore.com, pedro@codesourcery.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <833a63rbyd.fsf@gnu.org> References: <535d47e30909260627n662135a1hf6d1a0bb33368b3a@mail.gmail.com> <20090929015830.GJ9003@adacore.com> <1724490614004CEB9EE1A091A151E05B@xpjpn> <20090929042226.GK9003@adacore.com> <2C14068798BA41219F3603CDD24C8BC0@xpjpn> <20090929051929.GL9003@adacore.com> <7063C3E99BE344B2B98EDC0318ED852A@xpjpn> <20090929163910.GO9003@adacore.com> <93F096FEF7ED4579B52B23D69DA91195@xpjpn> <8363b0qm0n.fsf@gnu.org> <20090930201204.GH10338@adacore.com> <5650DA603A804427AA3B3F8F91164548@xpjpn> 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: 2009-10/txt/msg00002.txt.bz2 > From: Caz Yokoyama > Cc: , > > Date: Wed, 30 Sep 2009 20:48:37 -0700 > > Hello Joel and Eli, > Here is the patch which integrates your inputs. Even though I carefully look > through your inputs, there may be missing. Let me know if you find. Thanks. > --- gdb/NEWS 15 Sep 2009 03:30:04 -0000 1.331 > +++ gdb/NEWS 1 Oct 2009 03:32:18 -0000 > @@ -3,6 +3,9 @@ > > *** Changes since GDB 6.8 > > +* "set/show remotebreak" command is deprecated. Use "set/show remote > +interrupt-sequence" instead. I'd prefer this to be in the "New commands" section, even though it is not strictly speaking a new command. > +set remote interrupt-sequence [Ctrl-C | BREAK | SysRq-g] > +show remote interrupt-sequence > + Allow the user to select one of ^C, a break or Magic SysRq g as the > + sequence to the remote target in order to interrupt the execution. > + Ctrl-C is a default. Some system prefers BREAK which is high level of > + serial line for some certain time. Linux kernel prefers SysRq-g, a.k.a > + Magic SysRq. It is BREAK signal and character 'g'. ^^ Still one space. > - add_setshow_boolean_cmd ("remotebreak", no_class, &remote_break, _("\ > -Set whether to send break if interrupted."), _("\ > -Show whether to send break if interrupted."), _("\ > + add_setshow_boolean_cmd ("remotebreak", class_obscure, &remote_break, _("\ > +Deprecated. Use \"set remote interrupt-sequence [control-c|break]\" instead."), _("\ > +Deprecated. Use \"show remote interrupt-sequence\" instead."), _("\ You cannot have periods in the first line of the command's doc string. > +@item set remote interrupt-sequence > +@cindex interrupt remote programs > +@cindex select Ctrl-C, BREAK or SysRq-g > +Allow the user to specify what sequence @value{GDBN} sends to the remote target > +when you type @samp{Ctrl-c} to interrupt the program running > +on the remote target. Although @samp{Ctrl-C} is usually > +what remote systems expect (this is the default, here), it is > +sometimes preferable to send a @code{BREAK}. When debugging the Linux kernel, > +a @code{BREAK} followed by @code{g}, which is > +Magic SysRq g is required in order to interrupt the execution. Sorry, this still doesn't say what can be given to "set remote interrupt-sequence" to set the sequence, and does not clearly state the list of supported alternatives. > +Specify whether interrupt_sequence is sent ^^^^^^^^^^^^^^^^^^ Why do you use an underscore here?