From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Michael Snyder <msnyder@vmware.com>,
teawater <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 5/10
Date: Thu, 20 Nov 2008 09:00:00 -0000 [thread overview]
Message-ID: <20081120042153.GA6871@caradoc.them.org> (raw)
In-Reply-To: <1227153607.28256.106.camel@localhost.localdomain>
On Thu, Nov 20, 2008 at 02:00:07AM -0200, Thiago Jung Bauermann wrote:
> I'm fine with leaving 2 to be investigated/addressed when record adds
> support for its 2nd arch. It also may prove impractical, since there may
> be slight differences in syscalls for each arch.
Correct - there are slight differences, e.g. on LP64 platforms, and
especially in the layout of things like 'struct stat' - I don't know
if that's relevant here.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-20 4:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 2:18 teawater
2008-11-20 4:22 ` Michael Snyder
2008-11-20 8:33 ` Thiago Jung Bauermann
2008-11-20 9:00 ` Daniel Jacobowitz [this message]
2008-11-20 16:53 ` teawater
2008-11-24 16:50 ` teawater
2008-12-02 7:29 ` teawater
2008-12-19 7:23 ` 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=20081120042153.GA6871@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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