From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23592 invoked by alias); 1 Apr 2014 19:53:10 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 23512 invoked by uid 48); 1 Apr 2014 19:53:05 -0000 From: "jlebon at redhat dot com" To: systemtap@sourceware.org Subject: [Bug tapsets/16726] RFE: provide a way to retrieve tapset function types Date: Tue, 01 Apr 2014 19:53:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jlebon at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q2/txt/msg00001.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16726 --- Comment #2 from Jonathan Lebon --- Commit eb9ea96 added the --dump-functions switch. Sample output: user_ushort_warn:long (addr:long) /* myproc-unprivileged */ usrdev2kerndev:long (dev:long) ustack:long (n:long) usymdata:string (addr:long) /* myproc-unprivileged */ usymname:string (addr:long) /* myproc-unprivileged */ vers_from_clnt:long (clnt:long) vers_from_prog:long (program:long, vers:long) vm_fault_contains:long (value:long, test:long) warn:unknown (msg:string) /* unprivileged */ xid_from_clnt:long (clnt:long) As Josh mentioned, there is a risk that some types remain unresolved as they depend on how the user script uses them. For example, if we had the following tapset function: function my_func(x) { println(x) } it would show up in --dump-functions as: my_func:unknown (x:unknown) Thankfully, none of the current tapset functions have unresolved argument types according to the output of --dump-functions. Note that functions starting with '_' are hidden by default, use -v to show them. -- You are receiving this mail because: You are the assignee for the bug.