Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: 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 08:33:00 -0000	[thread overview]
Message-ID: <1227153607.28256.106.camel@localhost.localdomain> (raw)
In-Reply-To: <4924C246.6030104@vmware.com>

El mié, 19-11-2008 a las 17:49 -0800, Michael Snyder escribió:
> Thiago, you had a question about whether the syscall id numbers
> were invariant across architectures, and I think Hui answered that
> he was using the i386 numbering as representative, and would use
> a target-specific header file or something to translate them.
> 
> Or something to that effect.
> 
> Did that answer your concern?

I had two different but related concerns, regarding this 5th patch:

1. linux-record.c is really i386 specific, so it should be called
i386-linux-record.c.

2. If the information that needs to be recorded for each syscall (not
the syscall number) is the same accross architectures, the code in
linux-record.c could be made arch-independent and then we wouldn't need
to have this big chunk of code duplicated for each arch supporting
record functionality.

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.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2008-11-20  4:00 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 [this message]
2008-11-20  9:00     ` Daniel Jacobowitz
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=1227153607.28256.106.camel@localhost.localdomain \
    --to=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