From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19748 invoked by alias); 19 Oct 2007 06:32:08 -0000 Received: (qmail 19739 invoked by uid 22791); 19 Oct 2007 06:32:08 -0000 X-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,NO_REAL_NAME X-Spam-Check-By: sourceware.org Received: from mexforward.lss.emc.com (HELO mexforward.lss.emc.com) (128.222.32.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 19 Oct 2007 06:32:04 +0000 Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l9J6VtgE018829; Fri, 19 Oct 2007 02:31:56 -0400 (EDT) Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l9J6VPIh023530; Fri, 19 Oct 2007 02:31:53 -0400 (EDT) From: Yuxin_Zhuang@emc.com Received: from CORPUSMX60C.corp.emc.com ([10.254.64.72]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Oct 2007 02:31:42 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Subject: RE: Question about kernel module debug Date: Fri, 19 Oct 2007 06:32:00 -0000 Message-ID: <3807473EFFA73343902C7F097E26900001FA4448@CORPUSMX60C.corp.emc.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Question about kernel module debug Thread-Index: AcgRs+IWcNsjZeacQu66X007el2h3gAYdoWw References: <3807473EFFA73343902C7F097E26900001E981A6@CORPUSMX60C.corp.emc.com> <3807473EFFA73343902C7F097E26900001F48A6C@CORPUSMX60C.corp.emc.com> To: Cc: X-OriginalArrivalTime: 19 Oct 2007 06:31:42.0607 (UTC) FILETIME=[B68A79F0:01C81219] X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.8.30.53115 X-PerlMx-Spam: Gauge=, SPAM=1%, Reason='EMC_FROM_0+ -3, LOCALE_CHINESE 0, NO_REAL_NAME 0, __CHAR_CHINESE_CT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_CHARSET_FARAWAY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00207.txt.bz2 Configuration of my environment: Machine architecture: i686 OS: RHEL4 with kernel 2.6.9-42.Elsmp Systemtap version: 0.6 Elfutils : 0.129 GCC: 3.4.6 The content of the script ************************** probe module("my_module").function("*") { printf( "In the module\n"); } ************************** The output is as follows: ************************** Pass 1: parsed user script and 25 library script(s) in 80usr/10sys/136real = ms. semantic error: cannot find module my_module debuginfo: r_offset is bogus semantic error: no match for probe point while: resolving probe point module("my_module").function("*") Pass 2: analyzed script: 2 probe(s), 0 function(s), 0 global(s) in 0usr/30s= ys/43real ms. Pass 2: analysis failed. Try again with more '-v' (verbose) options. ************************** And the functions in kernel and modules built with the kernel can be probed= with no problem. The module 'my_module' has been built with the debug information not stripp= ed. But systemtap is still looking for a '.ko.debug' file. Thanks ! ZHUANG Yuxin -----Original Message----- From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org= ] On Behalf Of Frank Ch. Eigler Sent: 2007=C4=EA10=D4=C219=C8=D5 2:22 To: Yuxin, Zhuang Cc: systemtap@sources.redhat.com Subject: Re: Question about kernel module debug Yuxin_Zhuang@emc.com writes: > What do you mean by " There should be no need for the .ko.debug file > if the basic .ko file was not stripped. "?? Does it means that > systemtap will get the debug information from the .ko file and will > not look for the .ko.debug file on the three search paths?? That's right. > But when the .ko.debug symlink is removed, the result of strace > shows that without finding the '.ko.debug' file on the three search > paths systemtap just fails. Saying 'r_offset is bogus'. That's not right (elfutils error DWFL_E_BADRELOFF). It's as if something has corrupted the data. Please describe the toolchain version, architecture, and anything else that may be unusual about the build process. - FChE