This is the mail archive of the
mailing list for the Cygwin project.
AW: [bulk] - Re: One Problem solved other found -> dlclose not calling destructors
Wind Measurements & Power Curve Measurements
Tel.: +49 4421 4808 876
Fax: +49 4421 4808 843
DEWI GmbH - Deutsches Windenergie-Institut, Wilhelmshaven
Commercial Register No.: Amtsgericht Oldenburg, HRB 130241
Managing Director: Jens Peter Molly
Chairman of the supervisory board: Ministerialrat Dr. Niels Kämpny
P Please consider the environment before printing this email.
> Von: Christopher Faylor [mailto:firstname.lastname@example.org]
> Gesendet: Donnerstag, 4. Februar 2010 17:39
> An: email@example.com
> Betreff: [bulk] - Re: One Problem solved other found -> dlclose not calling
> On Thu, Feb 04, 2010 at 05:28:51PM +0100, DEWI - N. Zacharias wrote:
> >-----Urspr?ngliche Nachricht-----
> >> Von: Christopher Faylor [mailto:firstname.lastname@example.org]
> >> Gesendet: Donnerstag, 4. Februar 2010 16:30
> >> An: email@example.com
> >> Betreff: [bulk] - Re: One Problem solved other found -> dlclose not calling
> >> destructors
> There is way WAY too much unneeded cruft in your responses. You don't
> need any of the above. This makes it very hard to read your messages.
You are right! And I apologize for that.
But it is beyond my influence because our mailsverver add this crop.
I have talked to the admins and hope that they will fix it.
> >>On Thu, Feb 04, 2010 at 03:10:04PM +0100, DEWI - N. Zacharias wrote:
> >>>after Corinna solved the executable flag issue on NWFS another strange
> >>>thing happened.
> >>>I use Eclipse Version: 3.4.2 Build id: M20090211-1700 with the EPIC
> >>>Plugin to develop Perlscripts.
> >>>After installing the new cygwin1.dll which handles the NWFS execute
> >>>flag my debugger hangs at the stage 'launching delegate' .
> >>>Then Corrinna sends me a cygwin1.dll where the patch
> >>>http://cygwin.com/ml/cygwin-cvs/2010-q1/msg00065.html was not
> >>>With this dll the debugger works. So it seems that the patch has side
> >>Sorry but this really isn't very helpful. "With this dll the debugger
> >>works" doesn't provide enough details.
> >For details please ask Corrinna, she provides the dll which works.
> >>What destructors are not being called?
> >Sorry I don't know!
> Ok, so I guess your subject wasn't accurate.
I guess your guess is wrong!
Because with a dll
without the patch based on the issue eclipse/perl works
with the patch applied don't
So whats so hard to understand ??
> >I Only see the effect and Corinna tell me that she build the
> >Dll which works without the obove mentioned patch.
> >> Do you have a test case?
> >Get eclipse, install epic Perl Debug Plug-in 0.6.27 , write a simple perl script
> >#! /usr/bin/perl -w
> >print("hello world\n");
> >try to debug as Perl Local and you will see the debugger hanging around.
> >Sorry but neither I have the knowledge to figure out which call of perl
> >triggers the problem nor I have the time to get it.
> Sounds like we'll have to live with Eclipse not being able to debug perl
> locals then because I'm not going to break a long-running tradition of
> keeping all of my computers Eclipse-free.
First of all if you deciede not to use Eclipse because of religious believes it is ok!
Second I know it is hard to fix things if the reports are unspecific. But I'm really
not able to give more precise reports. Corinna send different dlls which
I tested according to her advice and give feedback. I suggest to do the
same in your case.
Third If the same Programm works well with one Version of Cygwin and not with
a newer Version of Cygwin it is not the fault of the Programm
Forth if the Programm did not work with a patch applied dll but without the patch
the reason has to do with the patch. Maybe not the patch itself but at least
with its side effects.
At least if this problem is not fixed we will just use the old cywin version which runs
without any problems and not stop using Eclipse/perl.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple