From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19332 invoked by alias); 2 Aug 2007 21:07:16 -0000 Received: (qmail 18935 invoked by uid 48); 2 Aug 2007 21:06:45 -0000 Date: Thu, 02 Aug 2007 21:07:00 -0000 Message-ID: <20070802210645.18934.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070802201140.4886.mmlnx@us.ibm.com> References: <20070802201140.4886.mmlnx@us.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/4886] stap should validate debuginfo files X-Bugzilla-Reason: AssignedTo 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-q3/txt/msg00241.txt.bz2 ------- Additional Comments From fche at redhat dot com 2007-08-02 21:06 ------- (In reply to comment #0) > As far as I can tell, stap relies solely on file/directory names to determine > which debuginfo files to use. It does not validate that, upon finding a match, > the debuginfo file is actually valid for the running kernel. It does a very limited amount of such checking at translation time. It could do more. We could e.g. extract init/version.c's init_uts_ns from the object file, and compare it to the module init-time utsname() results. Once the new build-id code is pervasive, it can be used as a stronger match check too. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4886 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.