From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10223 invoked by alias); 27 Dec 2012 21:13:46 -0000 Received: (qmail 10214 invoked by uid 22791); 27 Dec 2012 21:13:45 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 27 Dec 2012 21:13:36 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBRLDXMg020130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Dec 2012 16:13:33 -0500 Received: from host2.jankratochvil.net (ovpn-116-23.ams2.redhat.com [10.36.116.23]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id qBRLDTXs020646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 27 Dec 2012 16:13:32 -0500 Date: Thu, 27 Dec 2012 21:13:00 -0000 From: Jan Kratochvil To: Aleksandar Ristovski Cc: "gdb-patches@sourceware.org" Subject: Re: [patch] validate binary before use Message-ID: <20121227211328.GA5739@host2.jankratochvil.net> References: <50D4C49A.6040502@qnx.com> <50D8B37A.20001@qnx.com> <20121225073709.GA11349@host2.jankratochvil.net> <50DCAA5C.3000301@qnx.com> <20121227205924.GA5109@host2.jankratochvil.net> <50DCB787.6020601@qnx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50DCB787.6020601@qnx.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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 X-SW-Source: 2012-12/txt/msg00825.txt.bz2 On Thu, 27 Dec 2012 22:03:03 +0100, Aleksandar Ristovski wrote: > In any case, what I am trying to do does not disqualify build-id I understand that part but I find disappointing a feature designed specifically for this purpose and already deployed for 5+ years is being IIUC ignored. > (I'll use it in fact, if present). I do not see how you verify the NT_GNU_BUILD_ID content. > Note also that I really want a solution that does *not* rely on > section headers but rather only on load-time required stuff. build-id specifically does not depend on any link-time data (sections) to be usable for runtime core generations. It is (also) available from program header PT_NOTE as NT_GNU_BUILD_ID. Thanks, Jan