public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26181] New: tapset/linux/nfs_proc.stp needs update
Date: Mon, 29 Jun 2020 11:31:58 +0000	[thread overview]
Message-ID: <bug-26181-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26181
           Summary: tapset/linux/nfs_proc.stp needs update
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com
  Target Milestone: ---

Following testcase fails with recent stap:

=======
# cat nfs.proc.read_setup.stp 
probe nfs.proc.read_setup{
        printf("nfs.proc.read_setup server_ip: %s\n", server_ip);
        printf("nfs.proc.read_setup prot: %d\n", prot);
}

# stap -v -p 2 nfs.proc.read_setup.stp
Pass 1: parsed user script and 479 library scripts using
198280virt/79724res/10572shr/68976data kb, in 260usr/40sys/297real ms.
semantic error: type mismatch (string): identifier 'server_ip' at
nfs.proc.read_setup.stp:2:55
        source:         printf("nfs.proc.read_setup server_ip: %s\n",
server_ip);
                                                                      ^

semantic error: type mismatch (string): identifier 'server_ip' at :2:55
        source:         printf("nfs.proc.read_setup server_ip: %s\n",
server_ip);
                                                                      ^

semantic error: type was first inferred here (long): identifier 'server_ip' at
/usr/local/share/systemtap/tapset/linux/nfs_proc.stp:761:2
        source:         server_ip = 0
                        ^

semantic error: unknown type in dereference: operator '->' at
/usr/local/share/systemtap/tapset/linux/nfs_proc.stpm:26:13
        source:         ( @nfs_data->args->count )
                                   ^
        in expansion of macro: operator '@_nfs_data_args_count' at
/usr/local/share/systemtap/tapset/linux/nfs_proc.stp:792:10
        source:         count = @_nfs_data_args_count(@choose_defined($hdr,
$data))
                                ^

semantic error: unknown type in dereference: operator '->' at :26:13
        source:         ( @nfs_data->args->count )
                                   ^
        in expansion of macro: operator '@_nfs_data_args_count' at
/usr/local/share/systemtap/tapset/linux/nfs_proc.stp:824:10
        source:         count = @_nfs_data_args_count(@choose_defined($hdr,
$data))
                                ^

Pass 2: analyzed script: 3 probes, 26 functions, 2 embeds, 0 globals using
422524virt/305128res/11776shr/293220data kb, in 3450usr/580sys/4040real ms.
Pass 2: analysis failed.  [man error::pass2]
# 

=======

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

             reply	other threads:[~2020-06-29 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 11:31 mcermak at redhat dot com [this message]
2020-06-29 11:32 ` [Bug runtime/26181] " mcermak at redhat dot com
2020-06-29 14:36 ` mcermak 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-26181-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).