Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Sat, 26 Apr 2003 17:47:16 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Gerrit P. Haase" cc: Michael Lemke , Subject: Re: Perl instabilities In-Reply-To: <1939289495.20030426233458@familiehaase.de> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 26 Apr 2003, Gerrit P. Haase wrote: > Hallo Michael, > > Am Samstag, 26. April 2003 um 21:49 schriebst du: > > > Hi, I see the same. Haven't tried to track it down, though. > > When I run the perl Makefile.PL for the spamassassin 2.53 package > > perl crashes in CWD.DLL > > > micha> uname -a > > CYGWIN_98-4.10 micha 1.3.22(0.78/3/2) 2003-03-18 09:20 i586 unknown unknown Cygwin > > micha> perl -v > > > This is perl, v5.8.0 built for cygwin-multi-64int > > ... > > micha> perl Makefile.PL > > Checking if your kit is complete... > > Looks good > > Warning: prerequisite HTML::Parser 3 not found. > > 1924 [main] perl 898827 sync_with_child: child -861851(0xF0) died before initialization with status code 0xFFFFFFFF > > 2054 [main] perl 898827 sync_with_child: *** child state child loading dlls > > > After a while two instances (processes) of perl crash. > > [...] > > > Any ideas? > > There is a debudding versiopn of perl available: > Ok, a debugging version is here (two packages, 8MB sourcetree and > 10MB binaries): > http://koeln.convey.de/cywgin/perl/perl-5.8.0-debugging.tar.bz2 > http://koeln.convey.de/cywgin/perl/perl-5.8.0-debugging-srctree.tar.bz2 > http://koeln.convey.de/cywgin/perl/md5sums > > And a source package with the additional patches and scripts to > build a debugging version: perl-5.8.0-debugging-src.tar.bz2, is > available on request. > > As C. Faylor wrote: > > Now you could do something like: > > set CYGWIN=error_start=c:/cygwin/bin/gdb > > and when gdb pops up, type "bt" to get a stack trace. > Gerrit Gerrit, FYI, cmd.exe (and command.com) will barf at a "=" in a variable value. The following should work, though: set CYGWIN=error_start:c:/cygwin/bin/gdb Hope this helps, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- 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/