set -x for trace mode in Bash Scripting - Step-by-Step Execution

Concept Flow - set -x for trace mode

Start Script

↓

Enable set -x

↓

Execute commands

↓

Print each command before running

↓

Commands run with trace

↓

End Script

The script starts, enables set -x to print each command before execution, then runs commands showing trace output.

Execution Sample

Bash Scripting

set -x
name="Alice"
echo "Hello, $name!"

This script enables trace mode, sets a variable, and prints a greeting showing each command as it runs.

Execution Table

Step	Command	Trace Output	Action	Result
1	set -x		Enable trace mode	Commands will be printed before execution
2	name="Alice"	+ name=Alice	Assign variable	Variable name set to 'Alice'
3	echo "Hello, $name!"	+ echo Hello, Alice!	Print greeting	Output: Hello, Alice!
4	End of script		Script ends	No more commands

💡 Script ends after last command, trace mode stops with script

Variable Tracker

Variable	Start	After Step 2	Final
name	undefined	Alice	Alice

Key Moments - 3 Insights

Why do commands print with a '+' sign before running?

The '+' sign shows the command being traced because set -x is on, as seen in the Trace Output column in steps 2-3.

Does set -x change the commands or their results?

No, set -x only prints commands before running them; the commands and their results stay the same, shown in the Action and Result columns.

What happens if set -x is not used?

Commands run silently without printing each command line, so you won't see the trace output lines like '+ echo Hello, Alice!'.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'name' after step 2?

A "Alice"

B "Bob"

C undefined

D empty string

💡 Hint

Check the variable_tracker table under 'After Step 2' for 'name'

At which step does the script start printing commands before running them?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the Trace Output column in the execution_table; the first trace output is at Step 2

If we remove 'set -x', how would the Trace Output column change?

A It would show commands with '+' sign

B It would be empty for all steps

C It would show only the last command

D It would show error messages

💡 Hint

Without set -x, no commands are printed before execution, so Trace Output would be empty

Concept Snapshot

set -x enables trace mode in bash scripts
It prints each command before running it with a '+' prefix
Helps debug by showing command flow
Does not change command behavior or output
Use 'set +x' to turn off trace mode

Full Transcript

This example shows how 'set -x' turns on trace mode in a bash script. When enabled, each command is printed with a '+' sign before it runs. We start by enabling trace mode, then assign the variable 'name' to 'Alice', and finally print a greeting using echo. The execution table shows each step, the command run, the trace output, and the result. The variable tracker shows how 'name' changes from undefined to 'Alice'. Key moments clarify that the '+' sign means tracing, that set -x does not change command results, and that without set -x commands run silently. The quiz tests understanding of variable values, when tracing starts, and what happens if set -x is removed. The snapshot summarizes that set -x helps debug by printing commands before execution without changing their behavior.

Practice

1. What does the set -x command do in a bash script?

easy

A. It enables trace mode, showing commands as they execute.

B. It disables all script output.

C. It pauses the script until user input.

D. It clears all variables in the script.

Solution

1. Step 1: Understand the purpose of set -x

   The set -x command enables trace mode in bash, which prints each command and its arguments as they are executed.

2. Step 2: Compare with other options

   Other options like disabling output, pausing, or clearing variables do not match the behavior of set -x.

3. Final Answer:

   It enables trace mode, showing commands as they execute. -> Option A

4. Quick Check:

   set -x shows commands [OK]

Hint: Remember: -x means eXecute trace ON [OK]

Common Mistakes:

• Confusing set -x with set +x
• Thinking it pauses the script
• Assuming it clears variables

2. Which of the following is the correct syntax to turn off trace mode in a bash script?

easy

A. set -trace off

B. set -x

C. set +x

D. trace off

Solution

1. Step 1: Recall how to disable trace mode

   Trace mode is enabled with set -x and disabled with set +x.

2. Step 2: Check syntax correctness

   Options set -trace off and trace off are invalid bash commands.

3. Final Answer:

   set +x -> Option C

4. Quick Check:

   Disable trace with set +x [OK]

Hint: Use plus (+) to turn off options in bash [OK]

Common Mistakes:

• Using set -x to turn off trace
• Typing invalid commands like trace off
• Confusing with other shell options

3. Consider this bash script snippet:

#!/bin/bash
set -x
var=5
let var=var+3
echo $var
set +x
echo "Done"

What will be the output when this script runs?

medium

A. 5
8
Done

B. Syntax error at let command

C. var=5
var=var+3
8
Done

D. + var=5
+ let var=var+3
+ echo 8
8
+ set +x
Done

Solution

1. Step 1: Understand set -x effect

   With set -x, bash prints each command prefixed by '+', showing execution details.

2. Step 2: Trace commands and output

   Commands var=5, let var=var+3, and echo $var print with '+'. The echo outputs '8'. After set +x, only 'Done' is printed normally.

3. Final Answer:

   + var=5 + let var=var+3 + echo 8 8 + set +x Done -> Option D

4. Quick Check:

   Trace mode shows commands with '+' [OK]

Hint: Trace mode prints commands with '+' before output [OK]

Common Mistakes:

• Ignoring the '+' prefix in trace output
• Thinking trace mode changes variable values
• Assuming no command output is shown

4. You have this script snippet:

#!/bin/bash
set -x
for i in 1 2 3
  echo $i
done
set +x

What is the error and how to fix it?

medium

A. No error; script runs fine.

B. Missing 'do' after for loop; add 'do' before echo.

C. Missing quotes around $i; add quotes.

D. Incorrect use of set -x; remove it.

Solution

1. Step 1: Identify syntax error in for loop

   The for loop syntax requires 'do' before the commands to run in the loop.

2. Step 2: Fix the script

   Add 'do' after the for statement: for i in 1 2 3; do to fix the error.

3. Final Answer:

   Missing 'do' after for loop; add 'do' before echo. -> Option B

4. Quick Check:

   For loops need 'do' keyword [OK]

Hint: For loops always need 'do' before commands [OK]

Common Mistakes:

• Forgetting 'do' in for loops
• Removing set -x thinking it causes error
• Adding quotes unnecessarily around loop variable

5. You want to debug only a part of your bash script using trace mode. Which is the best way to do this?

hard

A. Put set -x before the part to debug and set +x after it.

B. Use set -x at the start and never turn it off.

C. Add set +x before and set -x after the part to debug.

D. Use trace on and trace off commands.

Solution

1. Step 1: Understand selective tracing

   To debug only a part, enable trace mode with set -x before that part and disable it with set +x after.

2. Step 2: Evaluate other options

   Using set -x always shows too much output; set +x before and set -x after reverses logic; trace on/off are invalid commands.

3. Final Answer:

   Put set -x before the part to debug and set +x after it. -> Option A

4. Quick Check:

   Toggle trace with set -x and set +x [OK]

Hint: Turn trace on/off around code to limit debug output [OK]

Common Mistakes:

• Leaving trace mode on for whole script
• Using invalid commands like 'trace on'
• Reversing set -x and set +x order