From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6722 invoked by alias); 14 Jul 2015 16:14:10 -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 6709 invoked by uid 89); 14 Jul 2015 16:14:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f176.google.com Received: from mail-ie0-f176.google.com (HELO mail-ie0-f176.google.com) (209.85.223.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 14 Jul 2015 16:14:08 +0000 Received: by iebmu5 with SMTP id mu5so14710753ieb.1 for ; Tue, 14 Jul 2015 09:14:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=mvc1clJRG8cPzAisjnZXjuRqCn+uHAenT2u8Lph1mzc=; b=kVE6NtVx6vqTMf7DV+RTZmZYhWDYXp8kI4D/FGtVh3ydGWOUmYcIY3MR6YqAcJN9SC hacrzgPpYE3ifENScb2nkZ17Emsyptud1pFDP11wvqFSdmLl15O3yTXHuA1nGPxmLc0N dBX64a9fSbFWP3GJK4AWutPazgidQFKBf1kXkDUHEvtiAqa7Xf91jj0T+5tOvxJ4/Al4 MbKfKtCQxwhycY4JXUWW8LoTaTeNFBtkFw7D0sgx3o4j+zfammYItDhSfPzB0X6A3ORw urXzv1QK6ciFJgigKWYIxkm0K7ORBt5nlPI7UWArlUPwDckHxLC9BLHtv46I5Yzz/ZXT 7NYQ== X-Gm-Message-State: ALoCoQn+hMe3Oqs1eFyEn8fYxba3zGaV1G2BoV+vkUndsjydOz6042GH40lVCiX9DZvfxOCz2gho X-Received: by 10.50.66.167 with SMTP id g7mr4542482igt.22.1436890446639; Tue, 14 Jul 2015 09:14:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.93.102 with HTTP; Tue, 14 Jul 2015 09:13:26 -0700 (PDT) In-Reply-To: <20150713123835.GA2529@host1.jankratochvil.net> References: <20150614192542.18346.87859.stgit@host1.jankratochvil.net> <20150614192655.18346.17075.stgit@host1.jankratochvil.net> <20150621101644.GA12733@host1.jankratochvil.net> <20150623204702.GA2156@host1.jankratochvil.net> <559D3749.9010200@redhat.com> <20150712190921.GA8682@host1.jankratochvil.net> <20150712192911.GB12553@host1.jankratochvil.net> <83vbdp8846.fsf@gnu.org> <55A39439.1090803@redhat.com> <20150713123835.GA2529@host1.jankratochvil.net> From: Doug Evans Date: Tue, 14 Jul 2015 16:14:00 -0000 Message-ID: Subject: Re: [PATCH v9 09/10] Validate symbol file using build-id To: Jan Kratochvil Cc: Pedro Alves , Eli Zaretskii , gdb-patches , Aleksandar Ristovski Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-07/txt/msg00411.txt.bz2 On Mon, Jul 13, 2015 at 5:38 AM, Jan Kratochvil wrote: > On Mon, 13 Jul 2015 12:34:33 +0200, Pedro Alves wrote: >> As the plan is for the feature to apply to the main executable too, >> it's better that "solib" isn't part of the setting name. I agree >> that "validate-build-id" sounds better than "build-id-validation". > > OK, so validate-build-id or solib-validate-build-id. > > Just this series being approved is still only for shlib and I do not yet have > completely finished the second series for all binaries; although 7.10 is > branched so till 7.11 there is now really enough time to have it all. > > So I do not know if I should call it in this shlib-only first series as > validate-build-id or as solib-validate-build-id. One of the important bits for me is to not add an option knowing we're going to rename it later. We've just branched 7.10 and I'm guessing all of this will be present for 7.11. So I'd be ok with just adding a simple note somewhere saying the option only applies to solibs at the moment and will eventually also apply to exes.