topic Re: Where to find one shell script editor in Operating System - HP-UX

Where to find one shell script editor

albert_hua — Wed, 10 Jul 2002 05:52:12 GMT

Hi, everyone:
I am a freshman towards shell script programming. Recently I have written a shell script which is about 300 sentences long. I just know to write a file with shell commands and then execute it directly under the current shell. Then some grammar errors occur. Grammar errors are relatively easy to position and correct but unfortunately there is some logical erros which are not easy to find without some tool aid. When I write C, I can find those logical errors easily with breakpoint or single step, etc. So I wonder whether there is some tools for shell programming providing the similar functions just as Turbo C. How and where can I get it? Thanks a lot!

Al.

Re: Where to find one shell script editor

Stefan Farrelly — Wed, 10 Jul 2002 05:54:24 GMT

When you run your script use the -x option and it will echo you every single line as it executes it so you can spot errors immediately.

eg.

sh -x ./<script> | more

Re: Where to find one shell script editor

Reinhard Burger — Thu, 11 Jul 2002 06:43:56 GMT

Hi Al
Just a small extension to the answer of Stefan.

if you use a tee in the pipe this will alow you to create a logfile. So you are able to read easily each script line and it's corresponding output.
In addition you can use the produced file for documentation ( if needed)

command will be then :

sh -x ./<script> | tee script.log | more

Re: Where to find one shell script editor

V. V. Ravi Kumar_1 — Thu, 11 Jul 2002 07:34:40 GMT

hi,

thereis nothing better than vi. but as already replied

sh -x <script> 2>&1 will give some info

insert some sleep or accepting input statements so that u can track.

regds

Re: Where to find one shell script editor

Steve Post — Thu, 11 Jul 2002 11:07:47 GMT

Sometimes I.....

Copy the busted piece of code to new, just to make sure it works the way I expect. Divide and conquer. When it works I copy it back into the program.

Add lines like this to the code....
#-----debugging-----------
echo "VAR should be skippy"
echo "VAR is $VAR"
echo "hit return to continue......"
read bogus_var
#-----debugging-----------
I get rid of the lines when it works right.

When I run the code I....
sh -xv myprog.sh 2>myprog.debug
Then vi file myprog.debug