This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Strange PATH behavior with 1.3.1
- To: cygwin at cygwin dot com
- Subject: Re: Strange PATH behavior with 1.3.1
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Tue, 1 May 2001 18:16:37 -0400
- References: <2C08D4EECBDED41184BB00D0B747334202FB4354@exchanger.cacheflow.com> <20010430180643.E1408@redhat.com>
- Reply-To: cygwin at cygwin dot com
On Mon, Apr 30, 2001 at 06:06:43PM -0400, Christopher Faylor wrote:
>On Mon, Apr 30, 2001 at 03:03:27PM -0700, Karr, David wrote:
>>I'd like to get some strace output. I really would. Running my script
>>with "strace -o strace.out -f <scriptname>" leaves me with an
>>"strace.out" file of zero size. It seems to not do anything when run
>>on a script.
>
>Don't run it on scriptname. strace is a mingw program (for hopefully
>obvious reasons). It can't execute shell scripts. You have to run it
>on the shell which is unable to find the scriptname. You indicated that
>scriptname ran correctly when invoked by hand so I don't see that any
>useful information would come about from running it via strace, even if
>it did work.
>
>If you really want to execute a script, the way to do it is:
>
>strace -owqwer sh script
>
>or, in your case:
>
>strace -owqwere sh -c "script"
So, I'm curious. What is the status of this problem?
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple