From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Marc Khouzam'" <marc.khouzam@ericsson.com>,
"'Joel Brobecker'" <brobecker@adacore.com>,
"'teawater'" <teawater@gmail.com>
Cc: "'David Daney'" <ddaney@caviumnetworks.com>, <gdb@sourceware.org>
Subject: RE: Discussing the next GDB release (GDB 7.0?)
Date: Tue, 20 Jan 2009 18:25:00 -0000 [thread overview]
Message-ID: <001a01c97b2c$75824960$6086dc20$@com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06C52409@ecamlmw720.eamcs.ericsson.se>
> For what its worth, I can't speak to the level of criticality of
> process record and replay, but we would really like to see this in
> the 7.0 release.
>
> I am almost ready with the Eclipse support for it (I manually
> applied the patches to GDB) and plan on doing a demo at EclipseCon.
> From what I was told, reverse debugging generates a lot of interest
> in people and would be a great addition to GDB.
>
> Great work on the whole Reverse Debugging feature and
> Process Record and Replay!
I wonder if record/replay and reverse debugging are one and the same feature
from the perspective of inclusion in gdb 7.0? It seems so from the above?
Logically, they can be separated into at least five parts:
* revexec support in gdb-serial
* reveexec support in MI
* revexec support in the gdb kernel
* record/replay as one way to effect revexec for the case of
x86-linux-user-process
* revexec from external sources, such as VMWare, Simics, and other simulators
Which parts of these are currently under consideration for inclusion in the
first 7.0 release?
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
________________________________________________________
next prev parent reply other threads:[~2009-01-20 18:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 3:46 Joel Brobecker
2009-01-15 4:18 ` Eli Zaretskii
2009-01-15 10:43 ` Vladimir Prus
2009-01-15 17:12 ` Joel Brobecker
2009-01-15 17:17 ` Tom Tromey
2009-01-15 17:24 ` Daniel Jacobowitz
2009-01-15 17:31 ` Joel Brobecker
2009-01-28 3:49 ` Thiago Jung Bauermann
2009-01-30 0:43 ` Joel Brobecker
2009-02-02 13:48 ` Thiago Jung Bauermann
2009-02-04 19:17 ` Tom Tromey
2009-02-06 0:48 ` Joel Brobecker
2009-01-15 17:24 ` David Daney
2009-01-15 17:37 ` Joel Brobecker
2009-01-15 23:54 ` teawater
2009-01-16 2:29 ` teawater
2009-01-16 3:40 ` Joel Brobecker
2009-01-16 6:32 ` teawater
2009-01-16 16:24 ` Tom Tromey
2009-01-16 14:30 ` Marc Khouzam
2009-01-20 18:25 ` Jakob Engblom [this message]
2009-01-21 0:18 ` teawater
2009-01-21 3:16 ` teawater
2009-01-27 5:09 ` Michael Snyder
2009-01-27 5:01 ` Michael Snyder
2009-01-30 0:48 ` Joel Brobecker
2009-01-16 3:47 ` Joel Brobecker
2009-01-16 5:48 ` Paul Pluzhnikov
2009-01-16 8:46 ` Eli Zaretskii
2009-01-16 14:55 ` Daniel Jacobowitz
2009-01-16 14:30 ` Joel Sherrill
2009-01-17 3:09 ` Joel Brobecker
2009-01-20 8:09 ` Nathan Sidwell
2009-01-20 10:41 ` Joel Brobecker
2009-01-20 11:25 ` Nathan Sidwell
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='001a01c97b2c$75824960$6086dc20$@com' \
--to=jakob@virtutech.com \
--cc=brobecker@adacore.com \
--cc=ddaney@caviumnetworks.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=teawater@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