From: Eliot Moss <moss@cs.umass.edu>
To: Sam Habiel <sam.habiel@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Help debugging a dll issue
Date: Fri, 20 May 2016 10:38:00 -0000 [thread overview]
Message-ID: <3a4d2501-8845-99b6-d58b-544bff5e223f@cs.umass.edu> (raw)
In-Reply-To: <CABHT960Yx_bg-NaHWcxePEV+Xz74NaVtsu+NjkrSZs4-62rCOA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-05-20 10:38 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 [this message]
2016-05-20 11:26 ` Duncan Roe
2016-05-20 12:02 ` Eliot Moss
2016-05-20 13:37 ` Duncan Roe
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=3a4d2501-8845-99b6-d58b-544bff5e223f@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=sam.habiel@gmail.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).