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 From: lemkemch AT t-online DOT de (Michael Lemke) To: cygwin AT cygwin DOT com Date: Mon, 28 Apr 2003 20:24:44 +0200 X-Priority: 3 (Normal) In-Reply-To: Message-Id: Subject: Re: Perl instabilities MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Sender: 520098960173-0001 AT t-dialin DOT net 4/27/03 21:29:20, Igor Pechtchanski wrote: >On Sun, 27 Apr 2003, Michael Lemke wrote: > >> 4/27/03 17:43:09, "Gerrit P. Haase" wrote: >> >> >Hallo Michael, >> > >> >>>>>>>> 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 >> > >> >>>Have you tried to rebase your installation? >> >>>Just type rebaseall in a bash shell. >> > >> >> What does that do? I remember some talk here but never >> >> understood it. Why would it be necessary? >> > >> >$ cat /usr/doc/Cygwin/rebase-2.2.README | more >> >> Thanks. Did that and followed the instructions to rebaseall. >> Same result with perl. :-( >> >> I then installed Gerrit's debug version and set CYGWIN=error_start:d:\cygnus\cygwin\bin\dumper.exe >> However, that doesn't work at all. dumper or gdb, which I tried first, isn't called at all. Instead there >> is this perl process sitting around that can't be killed and prevents a clean shutdown of Windows. >> The CYGWIN setting above has worked for me before. >> >> I further noticed the cwd.dll library, in which perl dies, is part of perl. >> Michael > >Michael, > >If you're setting it from bash, make sure to escape the backslashes (or >use forward slashes). You might also have to set error_start before >starting any Cygwin processes (if I'm wrong, someone please correct me)... Thanks for the warning, Igor. I set it in the .cmd file which starts my cygwin. To make sure I just ran a test case by writing a program that crashes. dumper started as supposed to. But it wrote an empty core file.... :-( Anyway, what next to try with perl? Could it have anything to do with threads? I just had the problem when I tried to build perl on VMS. Threads and 64bit stuff wouldn't work. Just a thought. Michael -- 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/