Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <43579205.1090801@scytek.de>
Date: Thu, 20 Oct 2005 08:48:05 -0400
From: Volker Quetschke <quetschke AT scytek DOT de>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Hang with 20051018 (3rd version) snapshot while building OOo
References: <4356A25A DOT 4080204 AT scytek DOT de> <20051019205011 DOT GA22512 AT trixie DOT casa DOT cgf DOT cx> <4356BF11 DOT 1090101 AT scytek DOT de>
In-Reply-To: <4356BF11.1090101@scytek.de>
Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";  boundary="------------enig7991003DD64BA032BA9BF896"
X-IsSubscribed: yes

--------------enig7991003DD64BA032BA9BF896
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Volker Quetschke wrote:
> Christopher Faylor wrote:
>>On Wed, Oct 19, 2005 at 03:45:30PM -0400, Volker Quetschke wrote:
>>(snip)
>>Given the number of changes that have been made to cygwin, particularly
>>in /proc handling, it's very difficult for me to believe that you are
>>not seeing *any* differences in behavior and
Well, there are differences in the frequency of occurrence of the hangs.

>> I'm wondering if you're
>>actually seeing what you think you're seeing, i.e., I'm wondering if the
>>process is just timing out and you are attributing it coming "unstuck"
>>to the fact that you're doing "ls /proc/*/fd".  I can't see any reason
>>why inspecting /proc should cause any kind of special behavior in the
>>latest snapshots since /proc handling now occurs in its own thread.
> 
> I can completely understand your worries. My problem is that I cannot
> reproduce the problem myself and all I can do is ask the people who
> have this problem to try get some debug information.
> 
> I just asked for a confirmation that it really is the "ls /proc/*/fd"
> that "unstucks" the process. I don't believe that "/usr/bin/tcsh -fc pwd"
> needs a long time to finish so that we're getting a coincidence there.
I got some information back:
It is done like this, the build is running/hanging in one shell (1).

When it hangs, start a new tcsh shell (2) and get the ps and cygcheck
information. Then open a new bash (3) and start "strace -p <pidhang>"
Now in (2) start
		while 1
			ls /proc/<pidhang>/fd
		end
until the strace is ready.

Some details: The build is running on a local NTFS drive. It's a dedicated
machine, not much is running beside the build.

He wrote that 20051019 also produced a hang and that I'll get the next ;)
strace.

Clueless

      Volker


> Having said that, I never realized that before, maybe the problem really
> lies in this special command. I mean due to some historic quirks every
> makefile in the OOo tree has a line that sets a macro to the current path
> using that command, but there are still lots of other commands (also executed
> in a tcsh shell) in these makefiles that I never heard of to hang.
> (I'll also verify that what I just said is really true, it's just an idea.)
> 
> 
>>I could almost convince myself that there was a race in /proc handling
>>before but I could never convince myself that doing something like "ls /proc/*/fd"
>>would have any effect on it.  Nevertheless, I did make some changes to
>>eliminate the potential source of hangs in this code.  So, I can't
>>understand why you wouldn't see something different.
> 
> 
> I have no clue either, especially as I also cannot reproduce and therefore
> cannot pinpoint the problem. :(
> 
> Anyway, thanks for all your efforts!
> 
>    Volker
> 


-- 
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D

--------------enig7991003DD64BA032BA9BF896
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDV5IKPTXJup+KeF0RApFvAJ44/WBsuAZlUDbfHllb5e1LdN4PsQCdE8ll
njSLwI1GRH+vMqQOf8yutA4=
=3AvY
-----END PGP SIGNATURE-----

--------------enig7991003DD64BA032BA9BF896--