From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21283 invoked by alias); 31 Jul 2007 21:59:27 -0000 Received: (qmail 21276 invoked by uid 22791); 31 Jul 2007 21:59:27 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 31 Jul 2007 21:59:22 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l6VLxKFC023757 for ; Tue, 31 Jul 2007 17:59:20 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l6VLxKF3025448 for ; Tue, 31 Jul 2007 17:59:20 -0400 Received: from [172.16.14.81] (tonsil.toronto.redhat.com [172.16.14.81]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l6VLxJJB007133 for ; Tue, 31 Jul 2007 17:59:19 -0400 Message-ID: <46AFB0B7.1040806@redhat.com> Date: Tue, 31 Jul 2007 21:59:00 -0000 From: Teresa Thomas User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: frysk@sourceware.org Subject: Debuginfo utilities added Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00249.txt.bz2 I have just merged my branch with the main branch and committed the changes. As mentioned earlier, I've added two new related utilities in frysk/frysk-core/bindir: 1) fdebuginfo - which lists the debuginfo paths for the (attached) process' modules. Its output format is a simple list of module names, followed by their debuginfo paths. Paths for ones that do not contain debuginfo, are shown as "---". 2) fdebugrpm - which is a bash script that allows you to install the missing debuginfo packages using yum. This lists the missing debuginfo packages, and gives the user a choice to install them. fdebugrpm internally runs fdebuginfo to obtain the names of the modules that are missing debugging information. For now, I suggest running fdebugrpm through the install tree (rather than the build tree) as the scripts direct it to look for fdebuginfo in this directory. This allows the scripts to be run from anywhere. An alternative, would be to ensure that the script and the utility it uses, are placed in the same directory and then direct the scripts to look for the utility in the same parent path as itself. Any suggestions between the two? Ideas on improving any other aspect of the utilities would be great too! Cheers, Teresa PS: To save the look up in case you don't have an install tree set up, passing ' --prefix=$PWD/installDirName' to frysk's configure makes one in the working directory.