Someone here might have played with this and know the answer.
I've a perl script with a header like this:
------
#!/usr/local/bin/perl -I /Users/amon/private_html/cgi-bin
etc
-----
Which is execle'd from a test program. Without the -I the process
always runs. With it, in usually doesn't on my home machine but
sometimes if I subshell (I'm already running in a csh by default)
it runs. If I go in via gdb I find that if I bpt just before the
call, and then continue, it usually works after giving a trap
which I also proceed from, but if I just run it it fails.
Have you had any similar long nights with execle()?
BTW - I'm passing it an environment with the SHELL set to /bin/csh.
I've a perl script with a header like this:
------
#!/usr/local/bin/perl -I /Users/amon/private_html/cgi-bin
etc
-----
Which is execle'd from a test program. Without the -I the process
always runs. With it, in usually doesn't on my home machine but
sometimes if I subshell (I'm already running in a csh by default)
it runs. If I go in via gdb I find that if I bpt just before the
call, and then continue, it usually works after giving a trap
which I also proceed from, but if I just run it it fails.
Have you had any similar long nights with execle()?
BTW - I'm passing it an environment with the SHELL set to /bin/csh.