From: William Cohen <wcohen@redhat.com>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
Cc: Guang Lei Li <liguangl@cn.ibm.com>, systemtap@sources.redhat.com
Subject: Re: Systemtap scripts unable to compile on RHEL4 U2
Date: Tue, 27 Sep 2005 19:15:00 -0000 [thread overview]
Message-ID: <43399A7E.5040802@redhat.com> (raw)
In-Reply-To: <44BDAFB888F59F408FAE3CC35AB470410222591E@orsmsx409>
Keshavamurthy, Anil S wrote:
<...>
> The above procedure is okay for the developers, but not advisable for
> end users I think.
> If Systemtap RPM is installed then all its dependencies should be met
> else I think there is some
> bug and people get confused.
Having a dependency on kernel-debuginfo is not going to work. It breaks
the way that the distribution set of rpms is computed. Red Hat doesn't
currently ship the kernel-debuginfo.
Also there is no guarantee that the kernel-debuginfo installed is the
one for the kernel being instrumented. It is quite possible to get
messages saying "no match for probe point" even with a kernel-debuginfo
installed if it doesn't match the kernel being instrumented.
SystemTap should be a bit more vocal when it is unable to find any
debuginfo for the kernel being instrumented, rather than having the
developer determine whether the debug information is missing or whether
the developer mis-typed the function name.
-Will
next prev parent reply other threads:[~2005-09-27 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 18:18 Keshavamurthy, Anil S
2005-09-27 19:15 ` William Cohen [this message]
2005-09-28 1:00 ` Vara Prasad
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 11:05 Frank Ch. Eigler
2005-09-26 22:59 Keshavamurthy, Anil S
2005-09-26 21:30 Keshavamurthy, Anil S
2005-09-26 22:23 ` Frank Ch. Eigler
2005-09-27 1:31 ` Guang Lei Li
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=43399A7E.5040802@redhat.com \
--to=wcohen@redhat.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=liguangl@cn.ibm.com \
--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).