From: "ocket8888 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/22772] missing kernel/module debuginfo for custom lt kernel
Date: Fri, 02 Feb 2018 17:21:00 -0000 [thread overview]
Message-ID: <bug-22772-6586-FJqPMmJr7e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22772-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22772
--- Comment #15 from ocket8888 <ocket8888 at gmail dot com> ---
(In reply to David Smith from comment #14)
> (In reply to ocket8888 from comment #12)
> > (In reply to Frank Ch. Eigler from comment #9)
> > > (In reply to ocket8888 from comment #6)
> > > > Created attachment 10773 [details]
> > > > strace output after attempting to probe kernel
> > >
> > > I meant
> > >
> > > % strace stap -p4 -e 'probe kernel.function("sys_open") {}'
> >
> > I uploaded the new output in 'strace.err' (output was only 62431 lines to
> > stderr, 0 on stdout)
>
> So, let's see where systemtap looked for the kernel's debug file (which
> should be at /usr/lib/debug/lib/modules/`uname -r`/vmlinux on a RHEL-type
> system):
>
> ====
> grep ^open strace_err.txt | fgrep ENOENT | fgrep
> '"/usr/lib/debug/lib/modules/' | fgrep vmlinux
> open("/usr/lib/debug/lib/modules/4.9.70-1.el7.centos.x86_64/vmlinux.debug",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/lib/debug/lib/modules/4.9.70-1.el7.centos.x86_64/vmlinux",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> ====
>
> So, where is the vmlinux file provided by your kernel-lt-debuginfo package?
```
$ ls -A /usr/lib/debug/lib/modules/`uname -r`
kernel
```
('kernel' is a directory) Also:
```
$ repoquery -l kernel-lt-debuginfo.x86_64 | grep vmlin
/usr/src/debug/kernel-lt-4.9.70/linux-4.9.70-1.el7.centos.x86_64/tools/perf/tests/vmlinux-kallsyms.c
```
So it doesn't appear to be providing one. Just to be safe, I ran:
```
$ find / -name '*vmlinux*'
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/scripts/gdb/vmlinux-gdb.pyc
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/scripts/gdb/vmlinux-gdb.py
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/scripts/gdb/vmlinux-gdb.pyo
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/scripts/link-vmlinux.sh
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/scripts/extract-vmlinux
/usr/src/kernels/4.9.70-1.el7.centos.x86_64/include/asm-generic/vmlinux.lds.h
```
and I'm not totally sure, but I don't think any of that helps... Could there be
something wrong with my spec file? Cuz it is generating the debuginfo package,
and I do have it installed, so the only thing I can think of is something weird
happening to its contents (disclaimer: I didn't write the spec file, a coworker
did).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-02-02 17:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:31 [Bug kprobes/22772] New: " ocket8888 at gmail dot com
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 [this message]
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-FJqPMmJr7e@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).