This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH v2 17/17] infrun: scheduler-locking reverse
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: markus dot t dot metzger at intel dot com, gdb-patches at sourceware dot org
- Date: Fri, 11 Sep 2015 12:02:16 +0300
- Subject: Re: [PATCH v2 17/17] infrun: scheduler-locking reverse
- Authentication-results: sourceware.org; auth=none
- References: <1441954298-25298-1-git-send-email-markus dot t dot metzger at intel dot com> <1441954298-25298-18-git-send-email-markus dot t dot metzger at intel dot com> <83io7h4eze dot fsf at gnu dot org> <55F2970D dot 6040603 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 11 Sep 2015 09:55:41 +0100
> From: Pedro Alves <firstname.lastname@example.org>
> CC: email@example.com
> 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., 
> 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.
>  - 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