X-Spam-Check-By:	sourceware.org
Date:	Tue, 11 Apr 2006 13:22:39 -0700 (PDT)
From:	Michael McKerns <mmckerns AT its DOT caltech DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	1.15.19 dlopen() dies with no dlerror()
Message-ID:	<Pine.GSO.4.58.0604111255381.25406@blinky>
MIME-Version:	1.0
X-Spam-Scanned:	at Caltech-ITS on water-dog by amavisd-2.3.3
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

---559023410-1903590565-1144786959=:25406
Content-Type: TEXT/PLAIN; charset=US-ASCII

I've been using the following Makefile syntax with building cygwin
applications:

$(PROJ_DLL) $(PROJ_SAR): product_dirs $(PROJ_OBJS)
	$(CXX) $(LCXX_SARFLAGS) -Wl,--out-implib=$(PROJ_SAR) \
	-o $(PROJ_DLL) $(PROJ_OBJS) $(LCXXFLAGS)

This is exactly what is in the cygwin documentation, but generalized
for Makefiles.  It has succesfully generated executables since way
back, and was still working for cygwin 1.15.18-3, however since I've
upgraded to 1.15.19-4 it fails.

The behavior is this:
Output from compile and build steps produce the expected linking
messages.  No apparent errors.

However, applications die at dlopen.

Example (1):
importing a shared library (journal) through python
 $ python -v
 ...
 >>> import journal
 import journal # directory /home/mmckerns/tools/.../journal
 ...
 dlopen("/home/mmckerns/tools/.../_journalmodule.dll", 2);

python dies here, and exits with no error.
That lead me to writing a little test script to check the
behavior of the .dll in C (without python).

Example (2):
testing a shared library (journal) with dlopen & dlerror
 $ ./dlopen.exe
 .dll TEST...

the executable dies here, and exits with no error or print
(please see attached dlopen.c)


I have a feeling that this might be related to previous reports
(such as http://sourceware.org/ml/cygwin/2006-04/msg00073.html
 and http://sourceware.org/ml/cygwin/2006-04/msg00036.html),
but I am not sure.

---

Mike McKerns
California Institute of Technology
---559023410-1903590565-1144786959=:25406
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dlopen.c"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine DOT GSO DOT 4 DOT 58 DOT 0604111322390 DOT 25406 AT blinky>
Content-Description: 
Content-Disposition: attachment; filename="dlopen.c"

I2luY2x1ZGUgPHN0ZGlvLmg+DQojaW5jbHVkZSA8ZGxmY24uaD4NCg0KaW50
IG1haW4oaW50IGFyZ2MsIGNoYXIgKiphcmd2KSB7DQogICAgdm9pZCAqaGFu
ZGxlOw0KLy8gIGRvdWJsZSAoKmNvc2luZSkoZG91YmxlKTsNCiAgICBjaGFy
ICplcnJvcjsNCg0KICAgIGZwcmludGYgKHN0ZG91dCwgIi5kbGwgVEVTVC4u
LlxuIik7DQovLyAgaGFuZGxlID0gZGxvcGVuKCIvaG9tZS9tbWNrZXJucy90
b29scy9weXRoaWEtMC44L21vZHVsZXMvYXJyYXlEZW1vL2FycmF5RGVtb21v
ZHVsZS5kbGwiLCBSVExEX0xBWlkpOw0KICAgIGhhbmRsZSA9IGRsb3Blbigi
L2hvbWUvbW1ja2VybnMvdG9vbHMvcHl0aGlhLTAuOC9tb2R1bGVzL2pvdXJu
YWwvX2pvdXJuYWxtb2R1bGUuZGxsIiwgUlRMRF9MQVpZKTsNCiAgICBpZiAo
IWhhbmRsZSkgew0KICAgICAgICBmcHJpbnRmIChzdGRlcnIsICIlc1xuIiwg
ZGxlcnJvcigpKTsNCiAgICAgICAgZXhpdCgxKTsNCiAgICB9DQogICAgZnBy
aW50ZiAoc3Rkb3V0LCAiLmRsbCBvcGVuZWRcbiIpOw0KDQovKiAgY29zaW5l
ID0gZGxzeW0oaGFuZGxlLCAiY29zIik7DQogICAgaWYgKChlcnJvciA9IGRs
ZXJyb3IoKSkgIT0gTlVMTCkgew0KICAgICAgICBmcHJpbnRmIChzdGRlcnIs
ICIlc1xuIiwgZXJyb3IpOw0KICAgICAgICBleGl0KDEpOw0KICAgIH0NCg0K
ICAgIHByaW50ZiAoIiVmXG4iLCAoKmNvc2luZSkoMi4wKSk7DQoqLyAgZGxj
bG9zZShoYW5kbGUpOw0KICAgIGZwcmludGYgKHN0ZG91dCwgIi5kbGwgY2xv
c2VkXG4iKTsNCiAgICByZXR1cm4gMDsNCn0NCg0K


---559023410-1903590565-1144786959=:25406
Content-Type: text/plain; charset=us-ascii

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
---559023410-1903590565-1144786959=:25406--

- Raw text -