From: Joel Brobecker <brobecker@adacore.com>
To: teawater <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Submit process record and replay third time, 1/9
Date: Fri, 09 Jan 2009 11:13:00 -0000 [thread overview]
Message-ID: <20090109111240.GK24105@adacore.com> (raw)
In-Reply-To: <daef60380901072144w79c11093g35e2cfb49db39ffb@mail.gmail.com>
> +# For the process record and replay target.
> +M:int:process_record:CORE_ADDR addr:addr
> +M:void:process_record_dasm:void
I haven't really followed the last discussions about recording
and reverse debugging. If these two methods are the way we decide
to go, could we document exactly what each method is expected
to do? This will help future implementors, I think.
--
Joel
prev parent reply other threads:[~2009-01-09 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 5:44 teawater
2009-01-09 11:13 ` Joel Brobecker [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=20090109111240.GK24105@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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