Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Process record and replay, 9/10
Date: Sat, 08 Nov 2008 09:25:00 -0000	[thread overview]
Message-ID: <uabcash7f.fsf@gnu.org> (raw)
In-Reply-To: <daef60380811072104j4e95269cmbf419cf575a90e66@mail.gmail.com>

> Date: Sat, 8 Nov 2008 13:04:13 +0800
> From: teawater <teawater@gmail.com>
> Cc: gdb-patches@sourceware.org
> 
> >> +   these macros are gotten from Linux Kernel source. */
> >> +#define I386_RECORD_SIZE__old_kernel_stat    32
> >> +#define I386_RECORD_SIZE_tms                 16
> >> +#define I386_RECORD_SIZE_loff_t                      8
> >> +#define I386_RECORD_SIZE_flock                       16
> >> +#define I386_RECORD_SIZE_oldold_utsname              45
> >> +#define I386_RECORD_SIZE_ustat                       20
> >
> > Shouldn't this kind of database be in the XML files just posted in the
> > "catch syscall" thread?
> >
> This is the size of variables in the Linux Kernel. I set it special
> because sometime this variables for each arches are not same.

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.


  reply	other threads:[~2008-11-08  9:25 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 [this message]
     [not found]       ` <20081110144014.GA12962@caradoc.them.org>
2008-11-10 20:45         ` Eli Zaretskii
2008-11-10 23:02           ` Michael Snyder
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=uabcash7f.fsf@gnu.org \
    --to=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