From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-36080-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 5174 invoked by alias); 24 Oct 2009 16:30:44 -0000
Received: (qmail 5123 invoked by uid 22791); 24 Oct 2009 16:30:40 -0000
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 	tests=AWL,BAYES_00,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, 24 Oct 2009 16:30:35 +0000
Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0KS100B0011ERS00@a-mtaout21.012.net.il> for gdb@sourceware.org; Sat, 24 Oct 2009 18:30:12 +0200 (IST)
Received: from HOME-C4E4A596F7 ([87.70.77.20]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KS100A7D1UBV440@a-mtaout21.012.net.il>; Sat, 24 Oct 2009 18:30:12 +0200 (IST)
Date: Sat, 24 Oct 2009 16:48:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Breakpoint commands
In-reply-to: <200910241704.00548.pedro@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83hbtog3fv.fsf@gnu.org>
References: <83iqe4g9t2.fsf@gnu.org> <200910241704.00548.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-10/txt/msg00353.txt.bz2

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 24 Oct 2009 17:03:59 +0100
> 
> "You can use breakpoint commands to start your program up again.  Simply
> use the @code{continue} command, or @code{step}, or any other command
> that resumes execution.
> 
> Any other commands in the command list, after a command that resumes
> execution, are ignored.  This is because any time you resume execution
> (even with a simple @code{next} or @code{step}), you may encounter
> another breakpoint---which could have its own command list, leading to
> ambiguities about which list to execute."

Thanks for reminding me.  We ought to display a warning when any
commands are used on the command list beyond those which resume.