From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [IPv6:2620:52:3:1:0:246e:9693:128c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 073261F4B4 for ; Tue, 22 Sep 2020 17:59:18 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id E549139878F5; Tue, 22 Sep 2020 17:59:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E549139878F5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1600797557; bh=weaXCV3u1bR4Ka9/GVDXYC+/yGbyLrewfd2PNa3eql0=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=FGS7wRh+USKxGjLsGXGznmZhVuybDiibDRKSyit4n7hHhFkWqYtxwqLp2kt8N3H8a 6xUnQcrVYS/B54RVB5iYoS/UzzVL7e/XbjpELKXVgtALNJFkXCqCOgzzUFGv3+Rzow QVUksnH46tTFfT3MjqtxhujNlEe49maRqwJURzW0= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id 6921539450C0 for ; Tue, 22 Sep 2020 17:59:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6921539450C0 Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-410-WRCnpmJOO8q1I6bFsJF5mA-1; Tue, 22 Sep 2020 13:59:12 -0400 X-MC-Unique: WRCnpmJOO8q1I6bFsJF5mA-1 Received: by mail-qv1-f72.google.com with SMTP id di5so12301849qvb.13 for ; Tue, 22 Sep 2020 10:59:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=weaXCV3u1bR4Ka9/GVDXYC+/yGbyLrewfd2PNa3eql0=; b=nloj1gxJiz03FM84XQL/ROn1lz67paCo5D9Ad5sJnINBbPSdKmrTGUv9oyh12GDbtv iDPdoigscxjVw4u5Bt6rgm2lLxm8bGbZMCIrmMqKDRQWjQZMRKRAljHOf0mdUcSssIm1 gtJ4f/1wzwsK24/ISFxYGE5uriyE1cUu7OP7VsCFVmEe7uUO5Dz7h7rVk/awcV6xThYx AmSyqh0fAko4xiPKChpMVmXaS4RursZ6jqieX2ZuoG97VotFsO6jO/afFPXjf6C50qWl o487zEYNUpsr4E65nbOuaBj6os10EU/G1bKxL25vjAXxheNDjg+Pon9GMskewSZ4NqqH anKg== X-Gm-Message-State: AOAM531Gen0hX9Fw3dypvM3oFmBbdKGuRIdXQy0hGpV3dMGirpX1LhNW sYTxfrykj0n9o1edlrAiiUZnINtmOYXoq1kGRwgmW60t4sKyBZdLnSx0/OIerJeLMriDo0ZbbXM i3Bcd+sozlFnxMkJC0IcO X-Received: by 2002:a37:480f:: with SMTP id v15mr5924694qka.279.1600797552129; Tue, 22 Sep 2020 10:59:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQIRLIY7O4rUFhPNHIrchnx+mBAN0+4VxBZNeQdfvnYM/No78WBVrMy5+y+K1H5clwj1iacw== X-Received: by 2002:a37:480f:: with SMTP id v15mr5924672qka.279.1600797551872; Tue, 22 Sep 2020 10:59:11 -0700 (PDT) Received: from [192.168.1.16] (198-84-214-74.cpe.teksavvy.com. [198.84.214.74]) by smtp.gmail.com with ESMTPSA id 192sm12586706qkn.9.2020.09.22.10.59.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Sep 2020 10:59:10 -0700 (PDT) Subject: Re: [RFC PATCH 0/3] implement dlmopen hooks for gdb To: Florian Weimer References: <20200626193228.1953-1-danielwa@cisco.com> <0f791d3a-20bc-4524-54eb-ce6df108fbff@redhat.com> <20200723184054.GD9875@zorba> <3ff42e45-b394-bf50-38c4-93baecc71497@redhat.com> <87h7rpwxke.fsf@oldenburg2.str.redhat.com> <87y2l1vhkn.fsf@oldenburg2.str.redhat.com> Organization: Red Hat Message-ID: Date: Tue, 22 Sep 2020 13:59:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <87y2l1vhkn.fsf@oldenburg2.str.redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Carlos O'Donell via Libc-alpha Reply-To: Carlos O'Donell Cc: Pedro Alves , "xe-linux-external\(mailer list\)" , Carlos O'Donell via Libc-alpha , "Jeremy Stenglein \(jstengle\)" Errors-To: libc-alpha-bounces@sourceware.org Sender: "Libc-alpha" On 9/22/20 1:37 PM, Florian Weimer wrote: > * Carlos O'Donell: > >> On 9/22/20 1:06 PM, Florian Weimer wrote: >>> * Carlos O'Donell via Libc-alpha: >>> >>>> Your next step would be to export the symbol via Versions at the current >>>> symbol node GLIBC_2.32 (soon to be GLIBC_2.33). >>> >>> Can we create a new GLIBC_DEBUG symbol versions for symbols which are >>> not intended to be used for run-time linking? >>> >>> The idea is that consumers will have deal with the absence of these >>> symbols anyway, so we just need one symbol version that does not depend >>> on the glibc version for this. Dependency management considerations >>> (that apply to symbols with run-time linking) do not come into play here. >> >> I don't object to GLIBC_DEBUG, like GLIBC_PRIVATE it can be considered >> a transient ABI that is valid only for a major release? > > No, unlike GLIBC_PRIVATE, you can assume that if a GLIBC_DEBUG symbol is > there (and perhaps has the documented size), it has the documented > semantics. But you can't assume that it is present. > > The semantics of GLIBC_PRIVATE symbols can change arbitrarily, even > between builds. Yes, absolutely, I agree completely, for it to be useful the semantics have to be: - If you detect a given symbol foo@GLIBC_DEBUG, then the feature is present and has the semantics you expect. - If you want new semantics then you need to make a foo2@GLIBC_DEBUG with the new semantics. What are the runtime semantics of the symbol? How do you access it? -- Cheers, Carlos.