From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24835 invoked by alias); 8 Jul 2005 17:45:47 -0000 Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Cygwin-Talk Malingering List Received: (qmail 24815 invoked by uid 22791); 8 Jul 2005 17:45:40 -0000 Received: from rohrpostix.convey.de (HELO rohrpostix.convey.de) (212.14.81.74) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Fri, 08 Jul 2005 17:45:40 +0000 Received: from [IPv6:::1] (unverified [212.14.81.76]) by rohrpostix.convey.de (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 08 Jul 2005 19:44:43 +0200 Message-ID: <42CEBB8B.3000508@familiehaase.de> Date: Fri, 08 Jul 2005 17:45:00 -0000 From: "Gerrit P. Haase" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 MIME-Version: 1.0 To: The Cygwin-Talk Malingering List Subject: Re: perl testsuite errors / cygserver not working / apache2 problems References: <42CD8654.2060903@familiehaase.de> <42CD8745.9080205@familiehaase.de> <42CD90A0.7080708@familiehaase.de> <03cf01c58336$cb60ab70$6508a8c0@chimaera> <42CE3FD7.3050109@familiehaase.de> <1431.130.240.136.130.1120826827.squirrel@pinus.tt.luth.se> <42CE95EB.9040803@familiehaase.de> <20050708172917.GH7507@calimero.vinschen.de> <20050708173434.GH18981@trixie.casa.cgf.cx> In-Reply-To: <20050708173434.GH18981@trixie.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q3/txt/msg00030.txt.bz2 Christopher Faylor wrote: > On Fri, Jul 08, 2005 at 07:29:17PM +0200, Corinna Vinschen wrote: > >>On Jul 8 17:04, Gerrit P. Haase wrote: >> >>>How to debug cygserver? >> >>-d option? GDB? > > > bash-3.00$ -d option? GDB? > bash: -d: command not found > > I think I've mentioned this before... Is cygwin broken? I have three computers with cygwin installed, on the first one I cannot fetch more than 8k from apache2 and I'm getting errors with the perl testsuite on IPC extensions. I think it is related. On the second box apache2 is working ok. I use the third box to build perl currently, here I get no errors for the pperl IPC tests. I cannot figure out what is different with the first box. Eg. I'm running postgreSQL which works fine, so basically everything seems to work, however there are these IPC errors from the perl tests. So s.th. is weird at this box. I'll try if the behaviour changes after a reboot. However I guess it will not because I had similar problems with apache2 before and similiar errors when building / testing perl. Gerrit