bash -x / trace / sdout
i've been going through some tutorials and one of the suggestions was to use the following at the beginning of your script to trace/debug:
Code:
#!/bin/bash -x Code:
bash myscript.sh Code:
#!/bin/bash any feedback would help, thanks. |
Hi
The "#!"sign in the first line first character in a file is a special character, wich is intended to give shell tips about the archive.
When you put "#! /bin/bash" you are telling shell to execute this file with bash, wich is a shell of coarse, or virtual shell wich mimics shell in graphical environ. "#! /usr/bin/env bash" do the same but thru env utility. Scripting file cannot have those lines, but it can cause troubles or unexpected behavior in certain cases. In python scripting one can put "#! /usr/bin/env python" so the shell won't try to execute this file sending it for python interpreter. The option -x in this case make bash more verbose, printing aliases and many stuffs in the prompt. Hope it helps |
That does help with the #! issue, i assumed something like that, but i wasnt sure.
but my -x issue is still there, maybe it would help if copied the script im trying to run. Code:
#!/bin/bash -x the script works. but as far as i know, using the -x should trace through the script, which is not what im getting when i run the script. ive tried using -x on other more complicated scripts and still, i can detect no change in the operation. im running debian if that has anything to do with anything. |
All I've ever done is use "set -x" after the #!/bin/bash first line. That will display everything as it is being processed. For example :-
#!/bin/bash set -x echo -n "Enter some text > " if read -st 2; then echo "Your wrote: $REPLY" else echo "Too slow suckah" fi |
Hi odimachkie
About -x in your script, traces its exec steps if you want some more advanced debugging try strace, ltrace or other tools. cheers |
thanks for the help everyone, i will be playing with ltrace and strace tonight, as armandrix mentioned.
but, for the record, i did figure out what my problem was. ive been running the scripts via the bash command, like so: Code:
odimachkie@LinuxBox:~/bin$bash myscript.sh i'm very obviously new at this, so thanks for the input everyone. every little bit helps. |
Actually, for full debugging, try
#!/bin/bash set -xv |
All times are GMT -5. The time now is 01:34 PM. |