From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-55828-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 25936 invoked by alias); 6 May 2008 03:15:43 -0000
Received: (qmail 25925 invoked by uid 22791); 6 May 2008 03:15:43 -0000
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.31) with ESMTP; Tue, 06 May 2008 03:15:23 +0000
Received: from HOME-C4E4A596F7 ([83.130.255.47]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K0F00A8PGCLBTO0@i-mtaout1.012.net.il> for gdb-patches@sources.redhat.com; Tue, 06 May 2008 06:29:09 +0300 (IDT)
Date: Tue, 06 May 2008 15:46:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] bpstat_do_actions in one place
In-reply-to: <20080505194130.GA20958@caradoc.them.org>
X-012-Sender: halo1@inter.net.il
To: Daniel Jacobowitz <drow@false.org>
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <u7ie8f7iz.fsf@gnu.org>
Content-transfer-encoding: 7BIT
References: <200804242002.03590.vladimir@codesourcery.com> <200805051304.05449.vladimir@codesourcery.com> <20080505114824.GB22274@caradoc.them.org> <200805051658.32272.vladimir@codesourcery.com> <uabj4ftmh.fsf@gnu.org> <20080505192315.GA19885@caradoc.them.org> <u8wyofsng.fsf@gnu.org> <20080505194130.GA20958@caradoc.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-05/txt/msg00229.txt.bz2

> Date: Mon, 5 May 2008 15:41:30 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
> 
> I wasn't worried about embedding the q in the breakpoint commands
> list, but about what effect it has when the prompt is triggered by
> a command in the breakpoint command list.  Basically, how far up
> the call stack is considered "the remaining output"?  Since what
> it actually does is abort the command, not just discard the output.

Okay, but is there a real problem here?  That is, can the user really
do something like that from inside breakpoint commands?  I think it's
not possible, since `q' is not a command.  Am I right?  If not, please
show an example of doing this from breakpoint commands, because I
cannot imagine a use case.