Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: atacama.four-d.de: mail set sender to using -f Message-ID: <3E783A20.9080204@gmx.net> Date: Wed, 19 Mar 2003 10:36:32 +0100 From: Thomas Pfaff User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Gerrit P. Haase" CC: cygwin@cygwin.com Subject: Re: Bleadperl on Cygwin with threads, 1 Test fails References: <67897318385.20030319075217@familiehaase.de> <3E7825B8.4050107@gmx.net> <27-1285058897.20030319093926@familiehaase.de> In-Reply-To: <27-1285058897.20030319093926@familiehaase.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gerrit P. Haase wrote: > Thomas schrieb: > > >>Gerrit P. Haase wrote: >> >>>Hallo perl5-porters, >>> >>>successfully builded bleadperl with threads the first time, >>>many thanks to the Wizard of Perl! >>> > >>I was able to build perl 5.8.0-1 with threads that has passed all tests >>by disabling perls internal malloc. With the perl malloc the embed test >>has failed. > > > You could build perl-5.8.0 with threads? I thought the 5.8. pumpking > fixed it just some days ago? Have you patched the sources? No. I took the cygwin perl-5.8.0-1 sources, configured and build it OOTB. It should build with the current cygwin dll. Do not try an older one, the latest cygwin dlls contain a number of fixes only to get perl with threads running. Mostly they were pthread_key and fork related. I had some problems with pthread_conds (some tests failed erratically) which are fixed in the CVS repository. The fixes should be in the next cygwin release. > > The embed test failure looks not like a problem with threads to me too, > lets wait for answers from the perl5-porters. Maybe. I noticed that the embed test has failed, debugged and recognized that the test failed due the perls internal malloc problems. If i remember right it was a segmentation violation. After i disabled perls malloc all tests have passed. I never build perl without thread support. Thomas -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/