From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
Sean Chen <sean.chen1234@gmail.com>,
Greg Law <glaw@undo-software.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: UndoDB's performance
Date: Fri, 18 Dec 2009 03:35:00 -0000 [thread overview]
Message-ID: <daef60380912171935w721cf97ay95e95d09b21850c2@mail.gmail.com> (raw)
In-Reply-To: <4B2A8DE9.5050200@vmware.com>
Maybe Marc use the record_wait in linux-nat.c version.
It will increase the speed a little.
I did some small test to add some record function to i386-linux-nat.c.
It will helpful.
The main speed issue is the prec need let the inferior keep single step.
So the prec skip patch can more helpful.
And the record part can be more intellective. For example:
Let record_message decode more than one code. Then we can let
inferior exec more than one insn for each cycle.
Thanks,
Hui
On Fri, Dec 18, 2009 at 04:00, Michael Snyder <msnyder@vmware.com> wrote:
> Marc Khouzam wrote:
>>
>> My results did seem suspiciously good. Trying things again, I don't
>> get the same results at all. I don't remember my exact orginal test,
>> but I know PRecord had a problem with recursion, maybe that is what
>> skewed the results?
>
> That problem with recursion was actually in gdb core, not in precord.
> As long as you're just executing (ie. not reverse-stepping) it would
> never have showed up.
>
> (and it's fixed now).
>
>
next prev parent reply other threads:[~2009-12-18 3:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:35 Sean Chen
2009-12-14 11:14 ` Hui Zhu
2009-12-14 13:18 ` Sean Chen
2009-12-14 15:08 ` Hui Zhu
2009-12-15 2:40 ` Sean Chen
2009-12-15 3:56 ` Hui Zhu
2009-12-15 7:26 ` Sean Chen
2009-12-15 9:11 ` Greg Law
2009-12-15 13:50 ` Marc Khouzam
2009-12-17 2:26 ` Sean Chen
2009-12-17 14:41 ` Marc Khouzam
2009-12-17 20:03 ` Michael Snyder
2009-12-18 3:35 ` Hui Zhu [this message]
2009-12-18 10:33 ` Sean Chen
2010-01-05 2:47 ` Hui Zhu
2010-01-05 15:34 ` Sean Chen
2010-01-06 3:14 ` Hui Zhu
2010-01-06 8:24 ` Sean Chen
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=daef60380912171935w721cf97ay95e95d09b21850c2@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=glaw@undo-software.com \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=sean.chen1234@gmail.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