All of lore.kernel.org
 help / color / mirror / Atom feed
From: lm@gate1-neteng.engr.sgi.com (Larry McVoy)
To: wje@fir.esd.sgi.com (William J. Earl)
Cc: linux@neteng.engr.sgi.com
Subject: Re: strace project
Date: Mon, 17 Jun 1996 15:27:36 -0700	[thread overview]
Message-ID: <199606172227.PAA23297@neteng.engr.sgi.com> (raw)

:        If by strace you mean tracing system call arguments and results,
: try using par(1).  (It does not help if you want to decode argument structures,
: however.)  Here is a sample:

He needs to decode args.  The idea was that strace groks most of the ioctls
in most OS's.  If we ever want to run little endian binaries on a big
endian kernel (which would be kinda cool) we need the arg decode.  David
wanted it for something else too.

--lm

WARNING: multiple messages have this Message-ID (diff)
From: lm@gate1-neteng.engr.sgi.com (Larry McVoy)
To: "William J. Earl" <wje@fir.esd.sgi.com>
Cc: linux@neteng.engr.sgi.com
Subject: Re: strace project
Date: Mon, 17 Jun 1996 15:27:36 -0700	[thread overview]
Message-ID: <199606172227.PAA23297@neteng.engr.sgi.com> (raw)
Message-ID: <19960617222736.l6bx7ifzk3ax2X7Pucwt1hSSqmtNMivM3Obb4CyO88I@z> (raw)

:        If by strace you mean tracing system call arguments and results,
: try using par(1).  (It does not help if you want to decode argument structures,
: however.)  Here is a sample:

He needs to decode args.  The idea was that strace groks most of the ioctls
in most OS's.  If we ever want to run little endian binaries on a big
endian kernel (which would be kinda cool) we need the arg decode.  David
wanted it for something else too.

--lm

             reply	other threads:[~1996-06-17 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-17 22:27 Larry McVoy [this message]
1996-06-17 22:27 ` strace project Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
1996-06-17 20:51 David S. Miller
1996-06-17 20:58 ` William J. Earl

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=199606172227.PAA23297@neteng.engr.sgi.com \
    --to=lm@gate1-neteng.engr.sgi.com \
    --cc=linux@neteng.engr.sgi.com \
    --cc=wje@fir.esd.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.