set -x for trace mode in Bash Scripting - Mini Project: Build & Apply

Using set -x for Trace Mode in Bash Scripts

📖 Scenario: You are writing a simple bash script to calculate the total price of items bought. You want to see each command as it runs to understand how the script works.

🎯 Goal: Learn how to use set -x to enable trace mode in a bash script and see the commands being executed.

📋 What You'll Learn

Create a variable with item prices

Enable trace mode using set -x

Calculate the total price using a loop

Print the total price with trace output visible

💡 Why This Matters

🌍 Real World

Trace mode helps developers debug bash scripts by showing each command executed. This is useful when scripts get complex or don't work as expected.

💼 Career

Knowing how to use <code>set -x</code> is important for system administrators, DevOps engineers, and anyone writing or maintaining shell scripts in professional environments.

1

Create a list of item prices

Create a bash array called prices with these exact values: 10, 20, 30.

Bash Scripting

# Create a bash array called prices with values 10, 20, 30
# Your code here

Hint

Use parentheses to create an array in bash, like array=(value1 value2).

2

Enable trace mode with set -x

Add the command set -x below the prices array to enable trace mode.

Bash Scripting

prices=(10 20 30)
# Enable trace mode
# Your code here

Hint

Just write set -x on a new line to turn on command tracing.

3

Calculate the total price using a loop

Create a variable total set to 0. Then use a for loop with variable price to iterate over ${prices[@]} and add each price to total.

Bash Scripting

prices=(10 20 30)
set -x

# Initialize total to 0
# Use for loop to add each price to total
# Your code here

Hint

Use total=0 to start. Loop with for price in "${prices[@]}". Add with total=$((total + price)).

4

Print the total price with trace output

Add a echo command to print Total price: followed by the value of total.

Bash Scripting

prices=(10 20 30)
set -x

total=0
for price in "${prices[@]}"; do
    total=$((total + price))
done

# Print the total price
# Your code here

Hint

Use echo "Total price: $total" to show the result.

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