Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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-Originating-IP: [66.167.206.172]
X-Originating-Email: [rkitover AT hotmail DOT com]
X-Sender: rkitover AT hotmail DOT com
From: "Rafael Kitover" <caelum AT debian DOT org>
To: <cygwin AT cygwin DOT com>
Subject: RE: Program randomly hangs after upgrading to cygwin 1.5.7
Date: Tue, 3 Feb 2004 15:14:49 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <40200EAE.9090701@scytek.de>
Message-ID: <BAY12-DAV639DYccSN000018fa2@hotmail.com>
X-OriginalArrivalTime: 03 Feb 2004 23:14:50.0130 (UTC) FILETIME=[85C82720:01C3EAAB]

>-----Original Message-----
>From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
>Volker Quetschke
>Sent: Tuesday, February 03, 2004 1:12 PM
>To: cygwin AT cygwin DOT com
>Subject: Re: Program randomly hangs after upgrading to cygwin 1.5.7
>
>Hi Rafael,
>> Are you using a win32 native compiled dmake or did you compile a copy of
>dmake
>> as a Cygwin binary? Either way, did you compile dmake with debugging
>support?
>
>as mentioned earlier in this thread, it is the cygwin binary. See the
>first message in this thread for cygcheck info of dmake, and the
>cygcheck output of my system.
>
>Thanks for looking at this
>
>   Volker

Just an idea that may be worth trying:

Make something like a /usr/local/bin/tracedmake

#!/bin/sh
strace -o /tmp/dmake-trace-$$ --flush-period=10 dmake $*

And try the build with MAKE=tracedmake, then when a make hangs, you should be
able to see the trace output in the last /tmp/dmake-trace* file for where or in
what process the dmake hangs.

Also if you compile dmake with debugging (gcc -g) you might then be able to
attach with CYGWIN=notty gdb --pid=<dmake-pid>.

If it's stuck inside the Cygwin dll, which is likely, then it would help to
compile the Cygwin dll from CVS, with --enable-debugging, and then you'd be
able to see where things are hanging in gdb with "dll cygwin1".

Also, any thoughts on how a smaller test case could be constructed without
trying to compile the whole of openoffice? Any pattern you notice about the
places where dmake hangs?

-- 
Rafael

--
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/