Write a tiny script that does something trivial in shell (e.g. "shell
ls"), and build that as a tiny executable.
Have your real script run that as a separate process and see if it never
returns.
(Hmmm ... can you always start another executable ?)
-- Alex.
On 14/10/2010 09:41, Monte Goulding wrote:
Hi Dar
Thanks for your interest.
I'm a little confused as to what is happening. Is the app locking up?
Yes. The shell function never returns. I have reported it as a bug because it
should fail gracefully. But I'd love a workaround or test.
Or does the function return empty?
If the latter, then maybe you can test shell with something trivial that always
returns something that is not empty. If you get empty, you can't use shell().
I wish it were that easy.
Cheers
Monte
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
