public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/20541] Systemtap 3.0 installation problem on Ubuntu 16.04 LTS @GCP
Date: Tue, 09 May 2017 15:36:00 -0000	[thread overview]
Message-ID: <bug-20541-6586-6aLQG3hfGl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20541-6586@http.sourceware.org/bugzilla/>

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2017-05-09
     Ever confirmed|0                           |1

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
Sorry for the delay.
It sounds as though the debuginfo-based probes (kernel.function) are getting
wrong addresses for your kernel, whereas the symbol-table-based ones
(nd_syscall*) are working.  I suspect a mismatch between your running kernel
and the exact dbgsym version installed.

The % stap-report 
program gathers information that may help further diagnosis.

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

  parent reply	other threads:[~2017-05-09 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  7:54 [Bug server/20541] New: " steve.tsai at nexusguard dot com
2016-08-31 13:47 ` [Bug server/20541] " fche at redhat dot com
2016-09-01  2:59 ` steve.tsai at nexusguard dot com
2017-05-09 15:36 ` fche at redhat dot com [this message]
2024-02-21 15:43 ` 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-20541-6586-6aLQG3hfGl@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).