From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14430 invoked by alias); 28 Aug 2009 10:05:41 -0000 Received: (qmail 14418 invoked by uid 22791); 28 Aug 2009 10:05:40 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_40 X-Spam-Check-By: sourceware.org Received: from dns.vtab.com (HELO oden.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 28 Aug 2009 10:05:32 +0000 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id A3E6A26EEDD; Fri, 28 Aug 2009 12:05:29 +0200 (CEST) Received: from polhem (unknown [62.20.90.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oden.vtab.com (Postfix) with ESMTP id 7C2C726EE98; Fri, 28 Aug 2009 12:05:29 +0200 (CEST) From: "Jakob Engblom" To: "'Eli Zaretskii'" Cc: References: <00cf01ca265a$d4110dc0$7c332940$@com> <83tyzucw8p.fsf@gnu.org> In-Reply-To: <83tyzucw8p.fsf@gnu.org> Subject: RE: GDB MI Reverse Commands added [2 of 3] Date: Fri, 28 Aug 2009 10:08:00 -0000 Message-ID: <002b01ca27c7$1316d8c0$39448a40$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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-08/txt/msg00511.txt.bz2 > > ! option is specified, resumes the reverse execution of the inferior > > ! program until a breakpoint is encountered, or until the inferior > > ! exits. >=20 > How can you exit in reverse? I think you can only get to the > beginning of `main', no? What about this? "Resumes the execution of the inferior program until a breakpoint is encountered, or until the inferior exits. If the @samp{--reverse} option is specified, resumes the reverse execution of the inferior program until a breakpoint is encountered, or until the execution reaches that start of the inferior. " Here, I generalize the "inferior" so that if debugging on naked hardware, e= xit really means the target rebooting or something like that.=20=20 > > ! Mode}), if the @samp{--all} is not specified, only the thread > > ! specified with the @samp{--thread} option (or current thread, if no > > ! @samp{--thread} is provided) is resumed.=A0 If @samp{--all} is >=20 > What `--thread' option are you talking about here? There was no such > option in the "Synopsis" part above. And I cannot see that the code parses it either... so it will be fixed. I apologize, but I am put as the messenger for a team effort...=20 /jakob