This is the mail archive of the
mailing list for the Cygwin project.
Re: dlopen() bug
- From: Gary Zablackis <gzabl at yahoo dot com>
- To: skaller <skaller at users dot sourceforge dot net>, Bernhard Loos <bernloos at web dot de>
- Cc: cygwin at cygwin dot com
- Date: Thu, 23 Mar 2006 06:02:59 -0800 (PST)
- Subject: Re: dlopen() bug
--- skaller <firstname.lastname@example.org> wrote:
> On Wed, 2006-03-22 at 03:35 +0100, Bernhard Loos
> > If the C++library declares its calls as 'extern
> "C"' (as it is done in the example),
> > AFAIK there shouldn't be any problem.
> Doesn't matter what you think you know -- it's not a
> permitted thing
> to do, you never know what implementors are going to
Who forbad it? A dll is just code which can be called
from any language as long as the interface rules are
followed by compilers, linkers and coders.
Anyway, the problem illustrated by the test case
occurs when a dll linked with -lstdc++ is dynamically
linked (via dlopen()) by a program which has not
previously initialized the standard library io
Running the testcase in gdb or with debugging print
statements added to cygwin1.dll shows this clearly.
Also, the problem persists if ct.c is changed to ct.cc
and g++ is used throughout in the build.
I have built debug versions of both cygwin1.dll and
libstdc++. I hope to have some time this weekend to
finally look into this problem more deeply.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html