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 [8.43.85.97]) (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 A2A201F4B4 for ; Tue, 22 Sep 2020 18:41:27 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 8BC9E398B853; Tue, 22 Sep 2020 18:41:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8BC9E398B853 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1600800086; bh=EV9c3UWhhO9bQxQrnwXHp6EJGeX1l0UkdzzgQM3wFIg=; 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=uJOiqxNw3hGV6u/y7kLRsyQR+OGI+FBQF9wUeKe4Y1FCC9ASQHWvj7prcMpnPxFxT vz+BVKoTTSW7n+E2RL4OxKCQlcPDDG8jFpYdPCbW2caxoRk+3h+51sBcBkg7h+B1OD vyxrD7TQM+9Xxju1gBK00QtSPJy+EmcskqRk1mDA= 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 279DB3987502 for ; Tue, 22 Sep 2020 18:41:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 279DB3987502 Received: from mail-qv1-f70.google.com (mail-qv1-f70.google.com [209.85.219.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-114-_-hGPmStN2KOC35p_eItxw-1; Tue, 22 Sep 2020 14:41:23 -0400 X-MC-Unique: _-hGPmStN2KOC35p_eItxw-1 Received: by mail-qv1-f70.google.com with SMTP id a20so12006048qvk.17 for ; Tue, 22 Sep 2020 11:41:23 -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=EV9c3UWhhO9bQxQrnwXHp6EJGeX1l0UkdzzgQM3wFIg=; b=Pw6383w5GcSIo/NaorbAllPgOw1a/mhDwCuhqRiUSFpQjlWo7ck3FvZ+aREqM9PFAJ D7h7p2xjkGwTM/4gBoM7xlbC8285IBL2wEEKQdDSx2wYC6+jnbXWPWLItvCU8ZAutAhu Sj31c7/WunpwAHBMCbDGObenjpVECAOuMpW9qEuQgeYMWOp0qToIIQtKevhBgv0Xcv6o 0W1uBdBEMrSlJg0zTgWwiw1UQfkMyNIuXNURo0j2G+3sR7rlhfCsjYanmZFQ28FTH//T gAx93dQc5MV51s66Rn3vo//ZTznb1Lt2oxZ8cwwjY9QHsFPN8+LVZtd0JEzhzUbDyVjl rY1Q== X-Gm-Message-State: AOAM533PqrtFVYayckj4ZanwwckwSKfTpuOuOj7is1V5El14sKashUl7 zCmD0TCaZ+lB6cwcSvhc2ZzxPWhVWS2i932+cUP7b/5tIpxOHv8BJAG2jtq88HXQD0+qdLAIbxU 5yeLn6M9znM1paPo1KTkA X-Received: by 2002:a0c:8d46:: with SMTP id s6mr7541415qvb.47.1600800082445; Tue, 22 Sep 2020 11:41:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzuxR3k22t3EiQOJOOqxa7nsrHzxjxsFSy/vqBYwnBaOTwGwyOKr2ZU3gQIaUtKZA9g6Wm7Yg== X-Received: by 2002:a0c:8d46:: with SMTP id s6mr7541200qvb.47.1600800079673; Tue, 22 Sep 2020 11:41:19 -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 m24sm12826455qtn.59.2020.09.22.11.41.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Sep 2020 11:41:18 -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> <87h7rpvgb4.fsf@oldenburg2.str.redhat.com> Organization: Red Hat Message-ID: <4b05c127-573a-2e9b-1147-18f827bfd07c@redhat.com> Date: Tue, 22 Sep 2020 14:41:17 -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: <87h7rpvgb4.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 2:04 PM, Florian Weimer wrote: > * Carlos O'Donell: > >>> 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? > > That obviously depends on the symbol? Sorry, I don't quite understand > these questions. You noted "not intended to be used for run-time linking?" Could you expand on what you're thinking there? -- Cheers, Carlos.