From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9725 invoked by alias); 14 Mar 2008 14:36:12 -0000 Received: (qmail 9702 invoked by uid 22791); 14 Mar 2008 14:36:10 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Mar 2008 14:35:44 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 84014983B5; Fri, 14 Mar 2008 14:35:42 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 219F7983AA; Fri, 14 Mar 2008 14:35:42 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JaB0W-0004uA-Uf; Fri, 14 Mar 2008 10:35:41 -0400 Date: Fri, 14 Mar 2008 14:36:00 -0000 From: Daniel Jacobowitz To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: enable a couple of useful cli commands in async mode. Message-ID: <20080314143540.GA18511@caradoc.them.org> Mail-Followup-To: Pedro Alves , gdb-patches@sourceware.org References: <200803140759.55397.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803140759.55397.pedro@codesourcery.com> User-Agent: Mutt/1.5.17 (2007-12-11) 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: 2008-03/txt/msg00171.txt.bz2 On Fri, Mar 14, 2008 at 07:59:55AM +0000, Pedro Alves wrote: > This is needed to test/develop async with CLI. The info info command is > very useful to debug gdb itself, and the interrupt command is needed to be > able to SIGINT the target. Without it, the user is trapped in the hole > of wanting to quit, but gdb complaining "I can't do that Dave" while the > target is running. "stop" is there already, so I added break too, > although it doesn't work yet. > > CLI command filtering this way is a gross hack that needs cleaning > up anyway. Since noone is using this currently, I went ahead and installed > as obvious. I'm confused by your choices. "stop" is not the command you think it is. There's a "stop_command" in breakpoint.c but that's the DBX-compatibility version of "break". The command "stop" doesn't do anything; it's only there for hook-stop. Also, how can we enable "info"? That will let you type "info regs" while the target is running; does something produce a useful error further down? "interrupt" makes sense. In fact I think this is what whoever added "stop" actually meant to add. -- Daniel Jacobowitz CodeSourcery