From: fche@redhat.com (Frank Ch. Eigler)
To: <webman@manfbraun.de>
Cc: <systemtap@sourceware.org>
Subject: Re: debian-problem (stretch/buster): Missing "-dbgsym", cannot run SystemTap
Date: Tue, 17 Mar 2020 18:46:52 -0400 [thread overview]
Message-ID: <87mu8eha5f.fsf@redhat.com> (raw)
In-Reply-To: <0a3001d5f8d4$2d3e9910$87bbcb30$@manfbraun.de> (webman@manfbraun.de's message of "Fri, 13 Mar 2020 02:10:24 +0100")
<webman@manfbraun.de> writes:
> [...]
> I looked around for hours, but the Debian packaging
> looks like a big PITA for me.
> Astoundingly, simple scripts run on Buster, but not
> on Stretch (which I cannot upgrade in the near future).
Yeah, it's clumsy.
If you are able, consider installing elfutils 0.178 or git-master
elfutils. You can build it into a private directory and direct
systemtap to use it with $LD_LIBRARY_PATH. With that available,
existing systemtap binaries can access our debuginfod server, and fetch
debug data for a selection of debian kernels.
https://sourceware.org/elfutils/Debuginfod.html
- FChE
next prev parent reply other threads:[~2020-03-17 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 1:10 webman
2020-03-13 10:31 ` Emanuele Rocca
2020-03-17 22:46 ` Frank Ch. Eigler [this message]
2020-03-20 5:24 webman
2020-03-20 16:17 ` Emanuele Rocca
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=87mu8eha5f.fsf@redhat.com \
--to=fche@redhat.com \
--cc=systemtap@sourceware.org \
--cc=webman@manfbraun.de \
/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).