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:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=WEdQ MOO19W9ghbVjXlI05d4Yu/WX9eEEqqQ9XyWYhN/4C/RlB2rrQQuPmLrzstyq3OGd 6nnfUavOfzaHylkMIn+d/lzhCXvzL2y+Pe2YWPWEtu/qysKT/W8UnEw4jgjSU879 4Ymiw+VpUWFeo8qEYo9W1VQorrPoPTMe4c7+b2Q= 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:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=rln/3zZYxr XeC3RmM5tTwj/8ng8=; b=v5qvt/92fQaKfllDE0l5hT8ryb7uD0WPZtEz6bfnwy /8oeJwzs6iLA08xSlOT7yfI1n6gCyWKgytVnJrCd4/R7cOyC7/HgfHsF6rMlzswi ee+cIhcn3cXFlr9N8+2A8HiYy5Iq0HKAHIZfwuef/clHNegLgaaZ3ncoEJ/bSD9t M= 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=1.6 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,RCVD_IN_SEMBACKSCATTER autolearn=no version=3.3.2 spammy=H*F:D*net.au, hth, HTH, findit X-HELO: mail106.syd.optusnet.com.au Date: Fri, 20 May 2016 23:36:59 +1000 From: Duncan Roe To: cygwin AT cygwin DOT com Subject: Re: Help debugging a dll issue Message-ID: <20160520133659.GD12938@dimstar.local.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <3a4d2501-8845-99b6-d58b-544bff5e223f AT cs DOT umass DOT edu> <20160520112618 DOT GC12938 AT dimstar DOT local DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=EfU1O6SC c=1 sm=1 tr=0 a=+cDhJlqnNvz9E7c5l3ERGg==:117 a=+cDhJlqnNvz9E7c5l3ERGg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=yrkiwgmsf1kA:10 a=QNbIVoj-GT2QqJOfW9gA:9 a=CjuIK1q_8ugA:10 X-IsSubscribed: yes 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. -- 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