set -x for trace mode in Bash Scripting - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does set -x do in a bash script?

set -x turns on trace mode, which shows each command and its arguments as they are executed. It helps you see what the script is doing step-by-step.

beginner

How do you turn off trace mode after using set -x?

You use set +x to stop showing commands in trace mode.

beginner

Why is set -x useful when writing bash scripts?

It helps you find mistakes by showing exactly what commands run and in what order, like watching the script work live.

beginner

Show a simple example of using set -x in a bash script.

#!/bin/bash set -x name="Alice" echo "Hello, $name" set +x echo "Done"

This script shows commands as they run until set +x.

intermediate

Can set -x slow down your script? Why or why not?

Yes, because it prints every command to the screen, which takes extra time and can clutter output.

What command turns on trace mode in bash?

A set +x

B trace on

C set -x

D debug start

set -x enables trace mode, showing commands as they run.

How do you stop trace mode in a bash script?

A set +x

B set -x

C stop trace

D unset trace

set +x disables trace mode.

What is the main benefit of using set -x?

A Hide commands from output

B See commands as they run for debugging

C Speed up script execution

D Automatically fix errors

Trace mode helps you debug by showing commands as they execute.

Which of these is a side effect of using set -x?

A Output becomes cluttered

B Commands are hidden

C Script runs faster

D Script stops on errors

Trace mode prints every command, making output longer and cluttered.

Where in a script should you place set +x?

A Before <code>set -x</code>

B At the very end only

C At the very start

D After you want to stop tracing

Use set +x where you want to stop showing commands.

Explain how set -x helps when debugging a bash script.

Think about how seeing each command helps you understand what the script does.

Describe how to use set -x and set +x in a script to control tracing.

Consider where you want to see commands and where you want normal output.

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