From: Duncan Roe <duncan_roe@acslink.net.au>
To: cygwin@cygwin.com
Subject: Re: Help debugging a dll issue
Date: Fri, 20 May 2016 13:37:00 -0000 [thread overview]
Message-ID: <20160520133659.GD12938@dimstar.local.net> (raw)
In-Reply-To: <dcfd0854-b7d0-9598-215c-a5f380b23968@cs.umass.edu>
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
next prev parent reply other threads:[~2016-05-20 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 2:54 Eliot Moss
[not found] ` <CABHT960Yx_bg-NaHWcxePEV+Xz74NaVtsu+NjkrSZs4-62rCOA@mail.gmail.com>
2016-05-20 10:38 ` Eliot Moss
2016-05-20 11:26 ` Duncan Roe
2016-05-20 12:02 ` Eliot Moss
2016-05-20 13:37 ` Duncan Roe [this message]
2016-05-20 13:46 ` Eliot Moss
2016-05-21 23:30 ` Eliot Moss
2016-05-22 1:46 ` René Berber
2016-05-22 2:53 ` Eliot Moss
2016-05-22 2:58 ` Duncan Roe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160520133659.GD12938@dimstar.local.net \
--to=duncan_roe@acslink.net.au \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).