From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9134 invoked by alias); 28 Sep 2005 11:05:52 -0000 Mailing-List: contact systemtap-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sources.redhat.com Received: (qmail 9000 invoked by uid 22791); 28 Sep 2005 11:05:41 -0000 Date: Wed, 28 Sep 2005 11:05:00 -0000 From: "Frank Ch. Eigler" To: systemtap@sources.redhat.com Subject: Re: Systemtap scripts unable to compile on RHEL4 U2 Message-ID: <20050928110533.GC16576@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-SW-Source: 2005-q3/txt/msg00621.txt.bz2 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