X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=iM7/nx7Y/fTc1c7S 9XdxAtgkLMqeip7UShetAJXKJi5Y1xR4g9K/rGbLR84XhggunQL291q5hUXMCSLs z3wumnSJa1zBbSPqh9wypI7+I1vgulJfLKltykwzC05KZ+R+YQ3v9vM01uzGydp+ df2TN/jtIi7I+GgPm/e9zw9mw84= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=k3gxGCDCEHP0J1d90ZhEH2 U8BPQ=; b=i8P7LC+f/lH9c6D/CWnBvkg2jYb5AAg4Ax+bc3aLRr4mapi63iutKH CLC5LrYPh/z0SDc8mOkoXJfjJWtNUa2GAJW+Hl68BW4I7m7gK7dgFlxauLYOSaXO vVEnl/KpVrDtCRjMl+JlMHwdfU10lntk2R54BpFBpYLoH9w+pZ6sM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Sam, H*f:sk:b21c0ab, Help X-HELO: csmail.cs.umass.edu Reply-To: moss AT cs DOT umass DOT edu Subject: Re: Help debugging a dll issue References: To: Sam Habiel , "cygwin AT cygwin DOT com" From: Eliot Moss Message-ID: <3a4d2501-8845-99b6-d58b-544bff5e223f@cs.umass.edu> Date: Fri, 20 May 2016 06:37:57 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 5/19/2016 11:28 PM, Sam Habiel wrote: > I had trouble with dlopen in Cygwin, where it did not behave intuitively. In my case, I was > dlopening libicu and friends. If you search using my name on the Cygwin mailing list, you should be > able to find out how I resolved the issue. I don't recall exactly what I did, but I think it was > that Cygwin put everything in a global namespace, and you need to dlsym NULL to grab the function > addresses. I just tried using NULL for the handle in dlsym, and I get the same result as before, and it does not change between using RTLD_LOCAL or RTLD_GLOBAL in dlopen. What I am seeing is that looking up one symbol is giving the value for a totally different one -- it's not returning an error indication. And this same wrong value is what happens if I just allow the natural linking to take place (which is what I really want to happen -- the dl calls simply help focus the issue). I will look up your previous issue, though, to see if there is something else there of use in this situation. Regards -- EM -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple