From: Michael Snyder <msnyder@vmware.com>
To: Greg Law <glaw@undo-software.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [discuss] Process record -- save and restore to a file
Date: Tue, 13 Oct 2009 20:30:00 -0000 [thread overview]
Message-ID: <4AD4E226.8090406@vmware.com> (raw)
In-Reply-To: <4AD4D027.8080806@undo-software.com>
Greg Law wrote:
> Michael Snyder wrote:
>> Greg Law wrote:
>>> Michael Snyder wrote:
>>>> [..]
>>>>
>>>> Secondly, I have a suggestion about the command names.
>>>> How about
>>>> record save <filename>
>>>> record restore <filename>
>>>> instead of
>>>> record dump <filename>
>>>> record load <filename>
>>>>
>>>> What do you guys think?
>>> UI looks good to me, too.
>>>
>>> Would we expect these commands to be reflected over the remote
>>> protocol if a remote target were using reverse debugging?
>> No, just as with core files, we've never made the final effort
>> to get gdb to suck all the information out of the remote target.
>>
>> And since this feature involves saving a core file, you can
>> imagine how much data we would be transporting.
>>
>> If we did corefiles first, I don't imagine it would be too hard
>> to get the rest of this to work.
>
> Oh, I wasn't imagining sucking the entire record log from the remote
> target into gdb. I was thinking of driving the saving/restoring of
> remote logs from gdb itself. So say you have gdb attached to a
> reversible debugging session on VMware or UndoDB or Simics or whatever,
> you could issue 'record save' and have the backend dump its log to disk
> in some format the backend understands. Likewise 'record restore' would
> cause send a packet to the backend causing the backend to suck in the
> logfile. The various backends could probably have their own interfaces
> to do this stuff, but it would seem nicer to have a "proper" interface
> for this at the gdb level.
Ah, I see. Yeah, that might be a good idea.
In my mind, the deciding factor (whether it's
worth doing) would be, could we get like three
back-end maintainers to agree on what would be
a useful syntax / semantics for them.
Say, you, VirtuTech and VMware?
There are probably a lot of other backend-specific things
that we could agree to do if they were common enough, but
that might be best done with monitor commands if not.
next prev parent reply other threads:[~2009-10-13 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:15 Michael Snyder
2009-10-12 17:13 ` Tom Tromey
2009-10-12 18:55 ` Eli Zaretskii
2009-10-12 22:58 ` Joel Brobecker
2009-10-13 6:19 ` Hui Zhu
2009-10-13 17:22 ` Michael Snyder
2009-10-13 18:45 ` Greg Law
2009-10-13 18:58 ` Michael Snyder
2009-10-13 19:08 ` Greg Law
2009-10-13 20:30 ` Michael Snyder [this message]
2009-10-14 1:52 ` Hui Zhu
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=4AD4E226.8090406@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=glaw@undo-software.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