public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Martin Hunt <hunt@redhat.com>
To: Hien Nguyen <hien@us.ibm.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: syscall tapset reorg again?
Date: Wed, 01 Mar 2006 18:32:00 -0000	[thread overview]
Message-ID: <1141237913.3385.22.camel@dragon> (raw)

Hien,

I checked in returnstr(). So a simple probe might look like this:

probe syscall.close {
        printf("%s: %s(%s) = ", execname(), name, argstr)
}

probe syscall.close.return {
        printf("%s\n", returnstr(returnp))
}

syscalls that return pointers should set returnp to 2 in
the return probe to indicate that returnstr should display the output in
hex.

---

I think it is time to attempt a reorganization of the syscalls. Actually
we probably should have done this first. Instead of syscalls.stp,
syscalls2.stp and aux_syscalls.stp, I think we need something like
syscall_net.stp, syscall_file.stp, syscall_process.stp, syscall_ipc.stp,
and syscall_misc.stp. This makes it easier to work on related syscalls.
Plus it should speed up the translation process. We can combine the
probes with the functions they use. Or perhaps it is better to put them
in their own set of files; net_funcs.stp, file_funcs.stp, etc. These
could be useful to script writers even if not using the syscall tapset.

Martin


                 reply	other threads:[~2006-03-01 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1141237913.3385.22.camel@dragon \
    --to=hunt@redhat.com \
    --cc=hien@us.ibm.com \
    --cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).