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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: 1.5.14-1: child died
Date:	Fri, 15 Apr 2005 13:43:43 +0100
MIME-Version:	1.0
In-Reply-To:	<425F81D4.3010105@vecernik.at>
Message-ID:	<SERRANOg9uV54Ogddu500000175@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	15 Apr 2005 12:43:38.0527 (UTC) FILETIME=[BF10E2F0:01C541B8]

----Original Message----
>From: Oliver Vecernik
>Sent: 15 April 2005 09:57

>>   Anyway, it could also be a permissions problem: maybe because its a
>> restricted user, the child process is in some way prevented from
>> accessing the object created by the parent and it can't notify it.  But
>> that's just guesswork.  I think your next most informative option might
>> be to use "strace -t"; that should let you see if there are any obvious
>> errors occurring in the child.
> 
> I don't know how to use this command, because I can't start any command
> within this user. Changing to another account I can't check it, because
> everthing works as expected. What exactly can I try?
> 
> 


  You can strace a program from a DOS prompt.  Cd into the cygwin bin
directory, and issue a command such as

strace -f -o strace.log -w --mask=all -b 204800 bash.exe --login -i


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -