Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Sun, 11 Jul 1999 17:21:26 +0400 From: Egor Duda X-Mailer: The Bat! (v1.029) S/N A0F2A05A Reply-To: Egor Duda Organization: DEO Message-ID: <14723.990711@logos-m.ru> To: Corinna Vinschen CC: cygwin-developers Subject: Re[2]: 19990705 snapshot References: <3787D6AE DOT 18EFE04B AT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! July 11 1999 Corinna Vinschen corinna AT vinschen DOT de wrote: CV> It was already clear but I got the same result (empty trace output) with CV> strace -f -o ls.out /usr/bin/ls -l CV> but now I have a new result: CV> This happens under tcsh only! With bash, trace is ok! CV> Why should the shell (the parent process of strace!) should have CV> any influence in that??? I'd encountered similar problems some time ago. It was because my win32 shell and bash had had different settings for $PATH. And in yet another occasion it was because of different $PATH values for local account and remote account i used through sshd. Could it be so in your case? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19