From: "ocket8888 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/22772] New: missing kernel/module debuginfo for custom lt kernel
Date: Thu, 01 Feb 2018 18:31:00 -0000 [thread overview]
Message-ID: <bug-22772-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22772
Bug ID: 22772
Summary: missing kernel/module debuginfo for custom lt kernel
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kprobes
Assignee: systemtap at sourceware dot org
Reporter: ocket8888 at gmail dot com
Target Milestone: ---
Created attachment 10770
--> https://sourceware.org/bugzilla/attachment.cgi?id=10770&action=edit
kernel configuration
I've been trying (and failing) to get systemtap to work on my CentOS machine.
```
$ uname -a
Linux ipcdn-cache-51.cdnlab.comcast.net 4.9.70-1.el7.centos.x86_64 #1 SMP
Thu Feb 1 15:34:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/centos-release```
CentOS Linux release 7.4.1708 (Core)
$ stap --version
Systemtap translator/driver (version 3.1/0.168, rpm 3.1-5.el7_4)
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.10-rc8
enabled features: AVAHI BOOST_STRING_REF DYNINST JAVA PYTHON2 LIBRPM LIBSQLITE3
LIBVIRT LIBXML2 NLS NSS READLINE
```
I'm attaching the configuration used to build the kernel, note that it follows
the configuration specified in the FAQ (Q2). When I run the test command `stap
-ve 'probe vfs.read{exit()}` it outputs
```
Pass 1: parsed user script and 529 library scripts using
378212virt/192180res/6484shr/188296data kb, in 2030usr/40sys/2078real ms.
semantic error: while resolving probe point: identifier 'kernel' at
/usr/share/systemtap/tapset/linux/vfs.stp:915:18
source: probe vfs.read = kernel.function("vfs_read")
^
semantic error: missing x86_64 kernel/module debuginfo [man
warning::debuginfo] under '/lib/modules/4.9.70-1.el7.centos.x86_64/build'
semantic error: resolution failed in alias expansion builder
semantic error: while resolving probe point: identifier 'vfs' at
<input>:1:7
source: probe vfs.read{exit()}
^
semantic error: no match
Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using
393364virt/210976res/10668shr/202812data kb, in 150usr/120sys/271real ms.
Pass 2: analysis failed. [man error::pass2]
```
However, I can show that I have installed all of the necessary packages:
```
$ yum list installed | grep kernel
kernel-lt.x86_64 4.9.70-1.el7.centos installed
kernel-lt-debuginfo.x86_64 4.9.70-1.el7.centos installed
kernel-lt-devel.x86_64 4.9.70-1.el7.centos installed
kernel-lt-headers.x86_64 4.9.70-1.el7.centos installed
kernel-lt-tools.x86_64 4.9.70-1.el7.centos installed
kernel-lt-tools-libs.x86_64
kernel-lt-tools-libs-devel.x86_64
```
note that the version numbers and release numbers match `uname -r`. As per the
FAQ (Q3), I've also verified that the kernel exists under /boot/:
```
$ ls /boot/ | grep `uname -r`
config-4.9.70-1.el7.centos.x86_64
initramfs-4.9.70-1.el7.centos.x86_64.img
symvers-4.9.70-1.el7.centos.x86_64.gz
System.map-4.9.70-1.el7.centos.x86_64
vmlinuz-4.9.70-1.el7.centos.x86_64
```
I'm not sure what else would be helpful, but I'm certainly willing to provide
any more information on request.
I suspect the problem has something to do with the fact that I'm using an lt
kernel, as `stap-prep` seems to be looking for the incorrect packages.
```
...
No package kernel-4.9.70-1.el7.centos.x86_64 available.
No package kernel-devel-4.9.70-1.el7.centos.x86_64 available.
No package kernel-debuginfo-4.9.70-1.el7.centos.x86_64 available.
...
```
not to mention that the proper - kernel-lt-* - packages are installed as noted
above.
To put it simply: what do?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-02-01 18:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:31 ocket8888 at gmail dot com [this message]
2018-02-01 18:52 ` [Bug kprobes/22772] " ocket8888 at gmail dot com
2018-02-01 18:53 ` ocket8888 at gmail dot com
2018-02-01 18:54 ` ocket8888 at gmail dot com
2018-02-01 19:29 ` dsmith at redhat dot com
2018-02-01 19:48 ` fche at redhat dot com
2018-02-01 20:53 ` ocket8888 at gmail dot com
2018-02-01 20:54 ` ocket8888 at gmail dot com
2018-02-01 20:55 ` ocket8888 at gmail dot com
2018-02-01 20:57 ` fche at redhat dot com
2018-02-01 21:02 ` ocket8888 at gmail dot com
2018-02-01 21:06 ` ocket8888 at gmail dot com
2018-02-01 21:07 ` ocket8888 at gmail dot com
2018-02-01 21:17 ` ocket8888 at gmail dot com
2018-02-01 22:38 ` dsmith at redhat dot com
2018-02-02 17:21 ` ocket8888 at gmail dot com
2018-02-02 17:23 ` fche at redhat dot com
2018-02-02 17:55 ` ocket8888 at gmail dot com
2018-02-02 17:56 ` ocket8888 at gmail dot com
2018-02-02 20:43 ` dsmith at redhat dot com
2018-02-06 16:20 ` ocket8888 at gmail dot com
2018-02-06 16:20 ` ocket8888 at gmail dot com
2018-02-06 16:23 ` ocket8888 at gmail dot com
2018-02-06 18:40 ` dsmith at redhat dot com
2021-08-06 1:28 ` lennordocdoc0921 at gmail dot com
2021-08-06 8:13 ` mark at klomp dot org
2021-08-06 12:07 ` dsmith 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-22772-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).