From: fche@redhat.com (Frank Ch. Eigler)
To: Esther Horbert <horbert@lfbs.RWTH-Aachen.DE>
Cc: systemtap@sources.redhat.com
Subject: Re: semantic error: libdwfl failure (dwfl_linux_kernel_report_modules): Exec format error
Date: Wed, 30 Jan 2008 17:21:00 -0000 [thread overview]
Message-ID: <y0modb3z0v9.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <47A0A7D7.6000201@lfbs.rwth-aachen.de> (Esther Horbert's message of "Wed, 30 Jan 2008 17:37:43 +0100")
Esther Horbert <horbert@lfbs.RWTH-Aachen.DE> writes:
> [...]
> We installed like described here:
> http://sourceware.org/systemtap/wiki/SystemtapOnDebian only installed
> the kernel manually (make install).
> Does somebody know what this Exec format error means and how to fix it?
> [...]
> # stap -vvv -e 'probe kernel.function("sys_open") {log("hello world")
> exit()}'
I note there is no systemtap version identification printed here.
This means that your copy of systemtap is pretty old.
> [...]
> semantic error: libdwfl failure (dwfl_linux_kernel_report_modules):
> Exec format error
> Ensure kernel debuginfo is installed
> [...]
More modern versions give a more precise error message.
Your elfutils is also rather aged. If you rebuild with a newer
systemtap (perhaps a cvs snapshot), consider also fetching a copy
of elfutils from http://sources.redhat.com/systemtap/ftp/elfutils
and using the "--with-elfutils=" bundling method.
>[...]
> # ls -l /boot/vmlinux-$(uname -r)
> -rwxr-xr-x 1 root root 43252479 2008-01-30 16:21 /boot/vmlinux-2.6.20-oprofile
That looks big enough to have all the dwarf data we could possibly want,
so you should not have to rebuild that nor reboot (if you're already running it).
- FChE
prev parent reply other threads:[~2008-01-30 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 16:38 Esther Horbert
2008-01-30 17:21 ` Frank Ch. Eigler [this message]
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=y0modb3z0v9.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=horbert@lfbs.RWTH-Aachen.DE \
--cc=systemtap@sources.redhat.com \
/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).