From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14720 invoked by alias); 9 Apr 2013 15:28:36 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 14628 invoked by uid 89); 9 Apr 2013 15:28:35 -0000 X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=ham version=3.3.1 Received: from na3sys009aog114.obsmtp.com (HELO na3sys009aog114.obsmtp.com) (74.125.149.211) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 09 Apr 2013 15:28:34 +0000 Received: from mx10.qnx.com ([209.226.137.110]) (using TLSv1) by na3sys009aob114.postini.com ([74.125.148.12]) with SMTP ID DSNKUWQzmktP0s7WfPza0lQNocPAGqpMQ3yF@postini.com; Tue, 09 Apr 2013 08:28:34 PDT Received: by mx10.qnx.com (Postfix, from userid 500) id 9471420E5F; Tue, 9 Apr 2013 11:28:19 -0400 (EDT) Received: from exhts.ott.qnx.com (exch1 [10.222.2.137]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx10.qnx.com (Postfix) with ESMTPS id 5F48820E1B; Tue, 9 Apr 2013 11:28:18 -0400 (EDT) Received: from qnxws8996.ott.qnx.com (10.222.2.5) by EXCH1.ott.qnx.com (10.222.2.137) with Microsoft SMTP Server id 14.2.318.4; Tue, 9 Apr 2013 11:28:18 -0400 From: Aleksandar Ristovski To: CC: , Aleksandar Ristovski Subject: [PATCH 0/8] v2 - validate binary before use Date: Tue, 09 Apr 2013 16:15:00 -0000 Message-ID: <1365521265-28870-1-git-send-email-ARistovski@qnx.com> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-04/txt/msg00232.txt.bz2 Hello, This patchset is updated patchset for using build-id to validate symbol file before use. I started the new thread as it unifies two other threads (see References below). Summary: Patchset introduces validation of symbol files prior to their use. If validation fails, symbol file is discarded. Validation is performed by comparing build-id from the target memory and that from the symbol-file. There are two methods for fetching build-id from the target memory: - using TARGET_OBJECT_LIBRARIES_SVR4 if target supports it - reading build-id directly if the above method is not supported. Core support: - core will use second method. Note, however, that due to (at least on ubuntu) not dumping page containing buid-id in the core, the validation can not be performed (it will always default to valid). This is misfortunate but outside the scope of this patch. References: http://sourceware.org/ml/gdb-patches/2013-04/msg00153.html http://sourceware.org/ml/gdb-patches/2013-04/msg00113.html Thank you, Aleksandar Ristovski QNX Software Systems