This is the mail archive of the
cygwin-xfree@sources.redhat.com
mailing list for the Cygwin project.
Re: xterm: Error 14, errno 2: No such file or directory problem with the current binaries at cygwin
- To: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Subject: Re: xterm: Error 14, errno 2: No such file or directory problem with the current binaries at cygwin
- From: Andrew Markebo <flognat at flognat dot myip dot org>
- Date: 18 Feb 2001 19:14:02 +0100
- Cc: "Mad Dave" <dave at ook dot demon dot co dot uk>, <cygwin-xfree at sourceware dot cygnus dot com>
- References: <005301c09984$145a7820$e682edc1@deepsleep><011901c09984$ff5bc130$0200a8c0@lifelesswks>
/ "Robert Collins" <robert.collins@itdomain.com.au> wrote:
| This is a special feature of cygwin's strace. It is a generic bug fixer. Seriously, try running a buggy program under strace. 9/10
| times, it'll work :-]
Hey this is not a generic cygwin feature, try your program in a
debugger, or even the development environment.. you will never find
any bugs there :-)
| > If I perform the following command
| >
| > rsh ntxserver "xterm -display mymachine:0 -e bash"
What happens if you give an absolute path to bash.exe or similar??
| > I get the following error
| >
| > xterm: Error 14, errno 2: No such file or directory
| >
| > But however if I run the xterm through strace with the following command
| >
| > rsh ntxserver "strace xterm -display mymachine:0 -e bash"
strace maybe loads in a bit of environment, path and so on when it
fires up bash...
/Andy