Ron Mansolino on 16 Sep 2009 04:26:15 -0700 |
as you've probably figured out; it's not that the shell can't find your executable, it's that your executable can't find something. but what? there are tools that will "trace" the execution of your program (on my debian, it's /usr/bin/strace) Script started on Wed 16 Sep 2009 07:24:35 AM EDT strace ping -c 1 localhost execve("/bin/ping", ["ping", "-c", "1", "localhost"], [/* 27 vars */]) = 0 brk(0) = 0x84a7000 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) mmap2(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ef2000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 etc... this generates a lot of spew, which is why we run it in a "script" session. but it will tell you which files it's checking status of (or more importantly, where) run it against things you're familiar with, so you can see how it works (eg. the "3" on the last line is a filehandle, you may see references later on that use that instead of a name)
On Tue, Sep 15, 2009 at 10:15 PM, Gordon Dexter <gordon@texasdex.com> wrote: My dad just got an Eee 900 with the default Linux install on it (which I ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|