-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have started my test script about half an hour ago, and it is still running. It never managed to do that before. This could be a good sign. Now, the snapshot DLL is far larger than the standard dll (I would ASSume because of debug info). Can the debugging info/additional baggage that is being carried around influence the normal runtime behaviour? Should I run strip against the snapshot DLL and rerun my test?
With kind Regards |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;, Volker Bandke |,4- ) )-,_. ,\ ( `'-' (BSP GmbH) '---''(_/--' `-'\_) Steinbach's Guideline for Systems Programming: Never test for an error condition you don't know how to handle. (Another Wisdom from my fortune cookie jar) -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.1 iQA/AwUBQgZgdx5trGyhAF0wEQKc5QCg51wnZdW5KOEQDiqtplfglygArXAAoJeH D4bXQSMUfTHe58WMpuIs1M96 =pPmL -----END PGP SIGNATURE----- -- 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/