This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [reverse] PATCH: Several interface changes
On Thu, Oct 9, 2008 at 10:49, Pedro Alves <pedro@codesourcery.com> wrote:
> On Thursday 09 October 2008 03:31:47, teawater wrote:
>> Maybe P record doesn't need make threads execute in different
>> direction. Cause P record reverse executes base on replay mode. This
>> mode will replay the memory change and the registers change. And all
>> threads of one process share the memory. So...
>
> You're thinking single-inferior. What about threads of different inferiors
> behind a single target_ops? Say, you're attached to process A, but you're
> leaving it running (you'll hit internal breakpoints in forward mode),
> while you're debugging/inspecting process B in reverse. There you have
> your two threads, on a single target, where the single per-target
> direction flag stops making sense.
If there are multi-inferior use different memory, it must need a flag in resume.
Sorry I am not make it clear in before.
>
> I understand the idealism behind this. I just posted the patch
> to show the direction I think we will end up taking, instead of
> trying to explain it by: "it would be nice if you did it the way
> I'm saying".
I always think GDB need it. :)
Thanks,
Hui