in reply to Any limitations to system() command?

To expand on what [id://Fletch] and [id://liverpole] have said, you should try to post the offending code here. However, before you do that, you really need to read How (Not) To Ask A Question, as it will help you avoid common mistakes that could result in unhelpful answers. Avoid painful lumps and bruises. Read How (Not) To Ask A Question.

I suggest that you pare down your code until it is the shortest possible script, yet still shows the error. If you haven't seen the answer then, go ahead and post the code here. In my experience (and many others here), the simple act of digging out the wayward code is enough to show you the error. Often it's obvious, but lost among all the other stuff going on.

And when you do post the code, use code tags: '<c>' and '</c>'. This will allow you to format the code so that it displays well, something your fellow monks will appreciate.

  • Comment on Re: Any limitations to system() command?

Replies are listed 'Best First'.
Re^2: Any limitations to system() command?
by magic_yang (Initiate) on Feb 28, 2006 at 01:48 UTC
    Maybe I wasn't clear, but $! solved the problem for me. Again, it was a memory allocation error.

    I would have posted the code if I thought it would've helped. But I was essentially looping on a print `$foo` command where $foo was a command execute proprietary software. Furthermore, that command worked for 12 cycles and also worked when I ran it outside of the script so I didn't think it was a syntax problem. I was just looking for more info on the nuances of running system() and commands through backticks. I did read How (Not) To Ask a Question, too.

    Anyways, it's been fun. Back to the world of hardware for me.