From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
"teawater@gmail.com" <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Process record and replay, 9/10
Date: Mon, 10 Nov 2008 23:02:00 -0000 [thread overview]
Message-ID: <4918A406.3020400@vmware.com> (raw)
In-Reply-To: <u1vxjqqgz.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Mon, 10 Nov 2008 09:40:14 -0500
>> From: Daniel Jacobowitz <drow@false.org>
>> Cc: teawater <teawater@gmail.com>, gdb-patches@sourceware.org
>>
>> On Sat, Nov 08, 2008 at 11:24:52AM +0200, Eli Zaretskii wrote:
>>> I understand that. I was asking whether we should store this
>>> information in the same place where we store all the other info about
>>> Linux system calls, not in the source.
>> Ideally, yes, I agree. But this is type layout rather than system
>> call information, and we haven't designed a way to store it in the
>> system call database yet. I'm sure we will at some point, but perhaps
>> we should address that afterwards instead of waiting?
>
> I'm fine with doing it later, if we can live with having the info in
> two places in the meantime.
Yes, I think later is good.
next prev parent reply other threads:[~2008-11-10 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 7:52 teawater
2008-11-07 14:53 ` Eli Zaretskii
2008-11-08 5:04 ` teawater
2008-11-08 9:25 ` Eli Zaretskii
[not found] ` <20081110144014.GA12962@caradoc.them.org>
2008-11-10 20:45 ` Eli Zaretskii
2008-11-10 23:02 ` Michael Snyder [this message]
2008-11-11 13:21 ` 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=4918A406.3020400@vmware.com \
--to=msnyder@vmware.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--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