From: teawater <teawater@gmail.com>
To: Jakob Engblom <jakob@virtutech.com>
Cc: gdb@sourceware.org
Subject: Re: Reverse excecution and Simics testing: short report
Date: Sat, 07 Feb 2009 06:18:00 -0000 [thread overview]
Message-ID: <daef60380902062218q16aab6aei808e71e4a88073fd@mail.gmail.com> (raw)
In-Reply-To: <029501c98854$2447b780$6cd72680$@com>
That is great! Thanks Jakob.
Hui
On Fri, Feb 6, 2009 at 20:12, Jakob Engblom <jakob@virtutech.com> wrote:
> Hi!
>
> We have done some preliminary "smoke testing" at Virtutech to see how
> gdb-main-branch revexec works with our old proven revexec engine. The results
> are quite encouraging.
>
> Simple testing using gdb-remote to talk to Simics, with Power Architecture and
> ARM targets appears to work. What worked in our specially-patched gdb-6.8
> version now works with gdb-trunk. We can stop and reverse and step etc.
> Essentially, this indicates that the reverse execution core support is OK.
>
> We also tested using MI commands to drive reverse execution. We used gdb-trunk
> plus our proposed MI commands, and the only problem we ran into seems to be the
> same reverse-finish (or preferably, uncall) operation that Teawater and Marc
> have been reporting. Once again, the system seems to be working fine overall.
>
> Best regards,
>
> /jakob
>
> _______________________________________________________
>
> Jakob Engblom, PhD, Technical Marketing Manager
>
> Virtutech Direct: +46 8 690 07 47
> Drottningholmsvägen 22 Mobile: +46 709 242 646
> 11243 Stockholm Web: www.virtutech.com
> Sweden
> ________________________________________________________
>
>
>
>
prev parent reply other threads:[~2009-02-07 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 12:12 Jakob Engblom
2009-02-07 6:18 ` 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=daef60380902062218q16aab6aei808e71e4a88073fd@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=jakob@virtutech.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