From: teawater <teawater@gmail.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
"Michael Snyder" <msnyder@specifix.com>,
"Thiago Jung Bauermann" <bauerman@br.ibm.com>
Subject: Re: GDB record patch 0.1.3.1 for GDB-6.8 release
Date: Wed, 11 Jun 2008 11:59:00 -0000 [thread overview]
Message-ID: <daef60380806110045g31e585a4w9b74b4b5bffa34c1@mail.gmail.com> (raw)
In-Reply-To: <200806090152.00220.pedro@codesourcery.com>
Hi Pedro,
> Don't worry, it's really more about code reorganization, than
> rewriting. :-)
>
> You have two major components in your patch.
>
> 1 - The record/replay component
> 2 - The inferior control in reverse execution mode.
>
> I'm suggesting to split those up, and make them communicate
> with an abstracted interface (target methods). In addition,
> make the record support a layer on top of the
> forward-execution-only debugging targets (of course, defering
> much to the arch support).
>
Michael Snyder is think about it too. He make a rev interface in
before. I will try to use it.
> My idea is that support for reverse execution should be exposed by
> target methods and properties. Say target_can_reverse_p (),
> target_set_execution_direction (...) or similar. For native
> debugging, it might be possible to share most of the code
> between similar targets.
>
> So, in a native linux debugging session, with record activated, the
> target stack would look this (ignoring the thread layer), top to
> bottom:
>
> target | stratum | supports reverse | Notes
> -------------+------------------+--------------------+-------------
> record | record_statum | 1 | (1)
> linux native | process_stratum | 0 | -
> exec target | file_stratum) | 0 | -
>
It's cool. But record only need the support of memory control and
register control from target. So I think most of target can support
record.
For the speed up, I change the code of Linux-Nat. But other target
such as "remote" still support by record.
The record need most support is from GDBARCH. It need add a function
like disassemble function in GDBARCH.
I think make record to be a target is very cool idea. But to implement
the current record. I have already changed a lot of code in GDB core
part. After I make record to a target, I think it maybe will still
have a lot of code in GDB core part. So make it to be a target is very
important?
Thanks,
Hui
next prev parent reply other threads:[~2008-06-11 7:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 8:55 Tea
2008-05-20 4:33 ` Thiago Jung Bauermann
2008-05-20 6:38 ` Daniel Jacobowitz
2008-05-20 15:32 ` Tea
2008-05-20 18:51 ` Michael Snyder
2008-05-21 17:26 ` Tea
2008-05-20 15:33 ` Tea
2008-05-21 17:14 ` Tea
2008-05-21 22:01 ` Michael Snyder
2008-05-21 22:16 ` Thiago Jung Bauermann
2008-05-21 22:40 ` Daniel Jacobowitz
2008-05-22 15:08 ` Thiago Jung Bauermann
2008-05-23 2:54 ` Tea
2008-05-23 4:33 ` Michael Snyder
2008-05-23 14:33 ` Tea
2008-05-23 16:46 ` Michael Snyder
2008-05-23 18:16 ` Tea
2008-05-23 3:52 ` Pedro Alves
2008-05-23 14:31 ` Tea
2008-05-23 21:10 ` Pedro Alves
2008-06-08 6:53 ` teawater
2008-06-09 0:52 ` Pedro Alves
2008-06-09 3:00 ` Daniel Jacobowitz
2008-06-09 13:58 ` Thiago Jung Bauermann
2008-06-10 2:04 ` Michael Snyder
2008-06-09 22:56 ` Michael Snyder
2008-06-11 11:59 ` teawater [this message]
2008-06-11 20:03 ` Michael Snyder
2008-06-12 18:10 ` teawater
2008-06-13 6:08 ` Michael Snyder
2008-06-14 6:24 ` teawater
2008-06-14 10:31 ` Michael Snyder
2008-06-15 3:27 ` teawater
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=daef60380806110045g31e585a4w9b74b4b5bffa34c1@mail.gmail.com \
--to=teawater@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.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