This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v2 17/17] infrun: scheduler-locking reverse

> Date: Fri, 11 Sep 2015 09:55:41 +0100
> From: Pedro Alves <>
> CC:
> 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] -
> 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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]