public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "aferrazz at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/16726] New: RFE: provide a way to retrieve tapset function types
Date: Wed, 19 Mar 2014 20:21:00 -0000	[thread overview]
Message-ID: <bug-16726-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16726

            Bug ID: 16726
           Summary: RFE: provide a way to retrieve tapset function types
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
          Assignee: systemtap at sourceware dot org
          Reporter: aferrazz at redhat dot com

Running 'stap -vp1' (verbose pass 1, with any provided script) outputs a dump
of all tapset contents; however, tapset functions and their parameters are
printed without their types.

It is possible to infer function & parameter types with pass 2, but that only
examines the functions which are called by a provided script.

I acknowledge that inferring the types of all functions & parameters of all
included tapsets may be processor-intensive, but it may be a useful optional
feature to have available.

For instance, SystemTap IDE for Eclipse (which I contribute to) features a
visual list of all tapset functions & their parameters, with icons next to each
entry to signify return & parameter types. At the moment, the only way to
obtain the types is to directly examine each function's definition in its host
tapset file (if it provides type information at all). In a case such as this,
being able to dump all tapset contents with types inferred would be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2014-03-19 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 20:21 aferrazz at redhat dot com [this message]
2014-03-20 19:55 ` [Bug tapsets/16726] " jistone at redhat dot com
2014-03-21 18:39 ` jlebon at redhat dot com
2014-04-01 19:53 ` jlebon at redhat dot com
2014-04-01 19:53 ` jlebon at redhat dot com

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=bug-16726-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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).