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=hvexOmIv7pIF3OiX D0MvyeZjTpb387lp8P0G1A7c0HbOP9OwT5zh8IQvx6orl0eGtXgQ5FyGYlj3yAhr o8dIYS5MWG9zTK2IxX4oC0bfTmVL8zhU0IsH96toTGgUJ2hEa6RwfitoI673FxPT 5DMQjtZmoVNmipanGzw5bbxwKhw= 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=4OCFhk1xr+PgxSqMWUszEp S0+qw=; b=VGcV2VdcNFID6zO5HGSH9b6iCCMjqmd9uGA43ChQgKLvoObo7jykKu VVfMzdDgI1FCRP3EdosrQolWP8RBzJliCTVnHLHs10zrcVYGdGU6/Don9NaRl+QT 6i653JcXS561GXnZHJEwjmX6IvYBrd3gepdy3yvIbXi5UUm0i6NNE= 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=Hx-languages-length:1349, findit, hth, HTH X-HELO: csmail.cs.umass.edu Reply-To: moss AT cs DOT umass DOT edu Subject: Re: Help debugging a dll issue References:

<3a4d2501-8845-99b6-d58b-544bff5e223f AT cs DOT umass DOT edu> <20160520112618 DOT GC12938 AT dimstar DOT local DOT net> <20160520133659 DOT GD12938 AT dimstar DOT local DOT net> To: cygwin AT cygwin DOT com From: Eliot Moss Message-ID: <739fe087-4386-3916-84e7-368ac27a5ae0@cs.umass.edu> Date: Fri, 20 May 2016 09:46:30 -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: <20160520133659.GD12938@dimstar.local.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 5/20/2016 9:36 AM, Duncan Roe wrote: > On Fri, May 20, 2016 at 08:02:20AM -0400, Eliot Moss wrote: >> On 5/20/2016 7:26 AM, Duncan Roe wrote: >> >>> Hi Eliot, >>> >>> Do you know what is the name of the totally different symbol? (maybe from nm -D) >> >> Yes -- I have been using nm and objdump to examine the relevant files. The dll >> is called libpypy-c.dll. The symbol I want to bind to is pypy_main_startup, and >> its proper value (as returned by nm and objdump) is 0x6410ac60. The result I >> get is the value of symbol pypy_g_PyNumber_Negative (an automatically generated >> C function), which is 0x63443f00. >> >> I wonder if these collide in some internal hash table and the hash lookup (or >> the table building) is broken in some subtle way. >> >> Regards -- Eliot >> > Does findit give the same answer for both symbols? > > If you could build your library and libdl.a with debug (-g) then you might be > able to see how the lookup goes wrong. > > HTH ... Duncan. Well, the wrong answer comes back from the Windows routine GetProcAddress. The bug seems to lie either in the Windows run-time code or in how the dll is being built. I am trying giving one of the functions a different name to see what happens (if it's a hash collision effect, presumably something will show up different). 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