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 translator/23074] New: unhandled DW_OP operation in DWARF expression
Date: Tue, 17 Apr 2018 14:43:00 -0000	[thread overview]
Message-ID: <bug-23074-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 23074
           Summary: unhandled DW_OP operation in DWARF expression
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com
  Target Milestone: ---

# stap --version; uname -r
Systemtap translator/driver (version 3.3/0.170, commit
release-3.2-170-g6cf36bad1fc1)
Copyright (C) 2005-2017 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 4.16-rc4
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON2 LIBRPM
LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE
4.14.0-49.el7a.x86_64
# 
# stap -e 'probe sunrpc.clnt.call_sync {exit()}'
semantic error: while processing probe
module("sunrpc").function("rpc_call_sync@net/sunrpc/clnt.c:1064") from:
sunrpc.clnt.call_sync from: sunrpc.clnt.call_sync

semantic error: unhandled DW_OP operation in DWARF expression [0] at 0 (250:
121165, 0): identifier '$clnt' at
/usr/local/share/systemtap/tapset/linux/rpc.stp:476:28
        source:                 __xprt = rcu_dereference($clnt->cl_xprt)
                                                         ^

semantic error: unhandled DW_OP operation in DWARF expression [0] at 0 (250:
121165, 0): identifier '$clnt' at :476:28
        source:                 __xprt = rcu_dereference($clnt->cl_xprt)
                                                         ^

semantic error: unhandled DW_OP operation in DWARF expression [0] at 0 (250:
121165, 0): identifier '$clnt' at :476:28
        source:                 __xprt = rcu_dereference($clnt->cl_xprt)
                                                         ^

semantic error: unhandled DW_OP operation in DWARF expression [0] at 0 (250:
121165, 0): identifier '$clnt' at :476:28
        source:                 __xprt = rcu_dereference($clnt->cl_xprt)
                                                         ^

semantic error: unhandled DW_OP operation in DWARF expression [0] at 0 (250:
121165, 0): identifier '$clnt' at :476:28
        source:                 __xprt = rcu_dereference($clnt->cl_xprt)
                                                         ^

Pass 2: analysis failed.  [man error::pass2]
#

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

             reply	other threads:[~2018-04-17 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 14:43 mcermak at redhat dot com [this message]
2018-04-17 16:49 ` [Bug translator/23074] unhandled DW_OP operation in DWARF expression (DW_OP_GNU_parameter_ref) mark at klomp dot org
2018-04-17 16:54 ` mark at klomp dot org
2018-11-13 16:08 ` fche 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-23074-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).