From: teawater <teawater@gmail.com>
To: "Pedro Alves" <alves.ped@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Resubmit process record and replay, 7/10
Date: Thu, 20 Nov 2008 16:37:00 -0000 [thread overview]
Message-ID: <daef60380811200032j122a90d6y9bf673ef19c7f174@mail.gmail.com> (raw)
In-Reply-To: <200811200250.22173.alves.ped@gmail.com>
Thanks Pedro,
Agree with your idea in record_wait part. Actually, I plan to do it
after P record check-in in the before.
Now, I will do it at once. :)
On the other hand, could you let me keep the code in linux-nat.c.
Because I think it can make linux-nat record speed up.
What about write a special function to check the breakpoint? Then both
linux-nat and record_wait can call it.
Hui
On Thu, Nov 20, 2008 at 10:50, Pedro Alves <alves.ped@gmail.com> wrote:
> On Thursday 20 November 2008 02:40:46, Pedro Alves wrote:
>
>> Can you please try moving all this blob...
>
> [...]
>
>> ... to the record target? It seems to be interested in getting
>> *all* events, instead of letting linux_nat_wait filter some.
>
> Sorry, reading back, I don't think I explained myself that well. I meant
> something like:
>
> ptid_t
> record_wait (ptid_t ptid, target_waitstatus *status)
> {
> while (1)
> {
> eptid = beneath->to_wait (ptid, &status);
>
> if (status.kind == TARGET_WAITKIND_TRAP)
> {
> if breakpoint_here (pc - pc_adjustement)
> {
> got breakpoint;
> break;
> }
> record_message ();
> beneath->resume (step);
> }
> else
> break probably.
> }
>
> if (got breakpoint)
> adjust_pc;
> return eptid;
> }
>
> --
> Pedro Alves
>
prev parent reply other threads:[~2008-11-20 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 2:35 teawater
2008-11-20 5:12 ` Michael Snyder
2008-11-20 15:19 ` teawater
2008-11-20 8:13 ` Pedro Alves
[not found] ` <200811200250.22173.alves.ped@gmail.com>
2008-11-20 16:37 ` 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=daef60380811200032j122a90d6y9bf673ef19c7f174@mail.gmail.com \
--to=teawater@gmail.com \
--cc=alves.ped@gmail.com \
--cc=gdb-patches@sourceware.org \
/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