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:to:from:subject:message-id:date :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=idYpeVDL+HOhHLTnM5xO5MMUnLychgQEzDkzT0Rfu4SxK4V54iqMx 2xPvAaQy2AmiLsz/sHZeYAbuHhgxSF5VAjDlPFukgMXMDXHALtXB4ylvUNX6OEhP Q34QLwJcMO2+P2p+/qWvZsEgSvpLQzN8pohOgzJ+8U+h1D+CyQB1rk= 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:to:from:subject:message-id:date :mime-version:content-type:content-transfer-encoding; s=default; bh=UXyzkacd0J+8bY7gO3FegyoOWKY=; b=ArheChF6+5TdVXNbgTY4pwI8UsZ5 3Y4mMijgAj38X00xGrjmrbASz4PB1K0ymHgXaAE3fSMfXLyN6crDVKd8mDSMMKF8 Sp3Ll0blvBUNhpb8DurX5A9Xub791jWd2uHTcxmQGyjy9R9HqOgjKzQrL4VP0BMW 1pntgUB8bE+nZiE= 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.2 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=moss, Moss, million, H*MI:341b X-HELO: csmail.cs.umass.edu Reply-To: moss AT cs DOT umass DOT edu To: cygwin From: Eliot Moss Subject: Help debugging a dll issue Message-ID: Date: Thu, 19 May 2016 22:54:29 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Dear Cygwin friends -- I am trying to get pypy to build under cygwin. (It used to do so, but has not been maintained.) I am very close, but there is something quite odd happening when trying to access the large dll that the system builds: the first call into that dll goes wild and causes a segfault. The issue seems to lie with run-time linking, for I can use dlopen to open the dll and then dlsym to look up the function, and I get the same bad address. I see nothing wrong from nm and objdump. The dll is about 70 million bytes long, so I can't really post it, but if you want to have a crack at this, we can find some mutually agreeable place and I can tell you the entry point I am trying to access. I have found that if I patch the indirection in the associated .exe file to refer to the actual address of the function, then the program runs, so it's just this one linkage that is not working (apparently). Very mysterious to me. Regards -- Eliot Moss -- 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