From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15201 invoked by alias); 11 Sep 2015 09:02:29 -0000 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 Received: (qmail 15190 invoked by uid 89); 11 Sep 2015 09:02:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout27.012.net.il Received: from mtaout27.012.net.il (HELO mtaout27.012.net.il) (80.179.55.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 Sep 2015 09:02:27 +0000 Received: from conversion-daemon.mtaout27.012.net.il by mtaout27.012.net.il (HyperSendmail v2007.08) id <0NUI00N008LPS100@mtaout27.012.net.il> for gdb-patches@sourceware.org; Fri, 11 Sep 2015 11:59:00 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout27.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NUI00DTF8YBDBB0@mtaout27.012.net.il>; Fri, 11 Sep 2015 11:59:00 +0300 (IDT) Date: Fri, 11 Sep 2015 09:02:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH v2 17/17] infrun: scheduler-locking reverse In-reply-to: <55F2970D.6040603@redhat.com> To: Pedro Alves Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838u8d49d3.fsf@gnu.org> References: <1441954298-25298-1-git-send-email-markus.t.metzger@intel.com> <1441954298-25298-18-git-send-email-markus.t.metzger@intel.com> <83io7h4eze.fsf@gnu.org> <55F2970D.6040603@redhat.com> X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00213.txt.bz2 > Date: Fri, 11 Sep 2015 09:55:41 +0100 > From: Pedro Alves > CC: gdb-patches@sourceware.org > > I'll admit that when reviewing this, I also noticed that the setting > applies both when stepping backwards, and when replaying forward, > and wondered whether that would be confusing. > > Do we call reverse execution "replay" too? The docs are a bit confusing > on this, sometimes it looks like we do, sometimes not. E.g., [1] > > When debugging in the reverse direction, gdb will work in replay mode as > long as the execution log includes the record for the previous instruction; > otherwise, it will work in record mode, if the platform supports reverse > execution, or stop if not. > > [1] - https://sourceware.org/gdb/onlinedocs/gdb/Process-Record-and-Replay.html#Process-Record-and-Replay > > I think the "If the platform supports reverse execution" part is talking > about when the remote target supports reverse debugging directly, > like e.g., Qemu / Simics / VMWare(?). > > But then it seems confusing to call reverse stepping "record mode", > as in "if it's rewinding time, what it is recording??". I'm okay with calling the value "reverse-execution". But "reverse" alone caused my brow to raise, since that value doesn't reverse anything.