From: teawater <teawater@gmail.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, "Michael Snyder" <msnyder@vmware.com>
Subject: Re: [reverse] PATCH: Several interface changes
Date: Thu, 09 Oct 2008 03:11:00 -0000 [thread overview]
Message-ID: <daef60380810082010o36309890t90ceb92c451376a6@mail.gmail.com> (raw)
In-Reply-To: <200810090349.37968.pedro@codesourcery.com>
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
prev parent reply other threads:[~2008-10-09 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 16:09 Pedro Alves
2008-10-08 7:28 ` teawater
2008-10-08 12:26 ` Pedro Alves
2008-10-08 20:21 ` Michael Snyder
2008-10-08 23:28 ` Pedro Alves
2008-10-09 2:32 ` teawater
2008-10-09 2:50 ` Pedro Alves
2008-10-09 3:11 ` teawater [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=daef60380810082010o36309890t90ceb92c451376a6@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox