public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: systemtap@sources.redhat.com
Subject: Re: Systemtap scripts unable to compile on RHEL4 U2
Date: Wed, 28 Sep 2005 11:05:00 -0000	[thread overview]
Message-ID: <20050928110533.GC16576@redhat.com> (raw)

Hi -

wcohen wrote:

> [...] SystemTap should be a bit more vocal when it is unable to find
> any debuginfo for the kernel being instrumented [...]

That's true.  At one point, it used to say so.


parasadav wrote:

> 1) Is it not a good idea as part of the very first check translator
> can do a version check between the debug info it is using and the
> version of the binary where it is going to insert probes?

While such a check would be prudent, at the moment it will never fail,
as systemtap/elfutils can select only the debuginfo for the currently
running kernel version/release.  It doesn't matter if other debuginfo
versions are installed - they won't be looked at.  (But see bug
#1145.)

> 2) If a customer upgrades the OS release how do we make sure the
> corresponding debug info matches without corresponding debug RPM's
> shipped.

We can't make sure of such a thing.  Users will need to update their
debuginfo's along with their kernels.  Users of RH packages may wish
to subscribe to this bug, until debuginfo distribution problems are
solved: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139767


- FChE

             reply	other threads:[~2005-09-28 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 11:05 Frank Ch. Eigler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-27 18:18 Keshavamurthy, Anil S
2005-09-27 19:15 ` William Cohen
2005-09-28  1:00   ` Vara Prasad
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=20050928110533.GC16576@redhat.com \
    --to=fche@redhat.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).