set -u for undefined variable errors in Bash Scripting - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output when using set -u with an undefined variable?

Consider this bash script snippet with set -u enabled. What will be the output or error?

Bash Scripting

set -u

echo "Value: $UNDEFINED_VAR"

A bash: UNDEFINED_VAR: unbound variable

B Value:

C Value: $UNDEFINED_VAR

D No output, script runs silently

💡 Hint

Think about what set -u does when a variable is not set.

The set -u option causes the shell to treat any attempt to use an undefined variable as an error. So, referencing $UNDEFINED_VAR will cause the script to stop and print an error message.

💻 Command Output

intermediate

How to safely use an undefined variable with set -u?

Given set -u is enabled, which command safely prints the value of MY_VAR without error if it is undefined?

Bash Scripting

set -u

# Which echo command below works safely?

A echo "$MY_VAR"

B echo "${MY_VAR+default}"

C echo "${MY_VAR?default}"

D echo "${MY_VAR:-default}"

💡 Hint

Look for the syntax that provides a default value if the variable is unset.

The ${VAR:-default} syntax returns default if VAR is unset or null, preventing errors with set -u.

🔧 Debug

advanced

Why does this script fail with set -u enabled?

Examine the script below. Why does it fail when set -u is set?

Bash Scripting

set -u

function greet() {
  echo "Hello, $1!"
}

greet $NAME

A Because $NAME is undefined and used without quotes

B Because $NAME is undefined and <code>set -u</code> causes an error on undefined variables

C Because $1 is undefined inside the function

D Because functions cannot access variables outside their scope

💡 Hint

Check which variable is undefined and how set -u treats it.

The variable $NAME is not defined before calling greet $NAME. With set -u, referencing an undefined variable causes an error.

🚀 Application

advanced

Modify this script to avoid errors with set -u

Given the script below, which modification prevents errors when set -u is enabled and CONFIG_PATH might be unset?

Bash Scripting

set -u

if [ -f "$CONFIG_PATH" ]; then
  echo "Config found"
else
  echo "Config missing"
fi

A if [ -f "${CONFIG_PATH?}" ]; then

B if [ -f "$CONFIG_PATH" ] 2>/dev/null; then

C if [ -f "${CONFIG_PATH:-}" ]; then

D if [ -f "$CONFIG_PATH" ] || true; then

💡 Hint

Use parameter expansion to provide a safe default for unset variables.

The ${VAR:-} syntax expands to an empty string if VAR is unset, preventing set -u errors.

🧠 Conceptual

expert

What is the main purpose of set -u in bash scripting?

Choose the best description of what set -u does in a bash script.

A It treats unset variables as an error and exits the script when they are used.

B It enables debugging mode to print each command before execution.

C It disables all variable expansions to improve performance.

D It automatically initializes all variables to empty strings.

💡 Hint

Think about how set -u helps catch mistakes with variables.

set -u makes the shell exit with an error if you try to use a variable that has not been set. This helps catch bugs early.

Practice

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

easy

A. Prints all variables and their values

B. Allows the script to continue even if variables are undefined

C. Stops the script if an undefined variable is used

D. Disables all error messages in the script

Solution

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

   The set -u option makes the script stop if it tries to use a variable that has not been set.

2. Step 2: Compare with other options

   Other options like continuing or printing variables do not match what set -u does.

3. Final Answer:

   Stops the script if an undefined variable is used -> Option C

4. Quick Check:

   set -u stops on unset variables [OK]

Hint: Remember: set -u = stop on unset variable [OK]

Common Mistakes:

• Thinking set -u ignores unset variables
• Confusing set -u with error message control
• Assuming it prints variables automatically

2. Which of the following is the correct way to enable set -u in a bash script?

easy

A. set -x

B. set -e

C. set +u

D. set -u

Solution

1. Step 1: Identify the correct option to enable set -u

   The command to enable the undefined variable error checking is exactly set -u.

2. Step 2: Understand other options

   set -x enables debugging, set +u disables set -u, and set -e stops on any error, not specifically unset variables.

3. Final Answer:

   set -u -> Option D

4. Quick Check:

   Enable set -u with set -u [OK]

Hint: Use set -u exactly to enable undefined variable errors [OK]

Common Mistakes:

• Confusing set -u with set -x or set -e
• Using set +u which disables the feature
• Forgetting the dash before 'u'

3. What will happen when running this script with set -u enabled?

#!/bin/bash
set -u

echo "Hello $NAME"

medium

A. Stops with an error without printing anything if NAME is not set

B. Prints 'Hello $NAME' literally without substitution

C. Prints 'Hello' followed by the value of NAME if set, else empty

D. Ignores the unset NAME and prints 'Hello '

Solution

1. Step 1: Understand set -u effect on unset variables

   With set -u, using an unset variable like NAME causes the script to stop with an error.

2. Step 2: Analyze the script behavior

   The script tries to print $NAME which is not set, so it will stop and show an error instead of printing anything.

3. Final Answer:

   Stops with an error without printing anything if NAME is not set -> Option A

4. Quick Check:

   Unset variable with set -u causes error [OK]

Hint: Unset variable with set -u stops script immediately [OK]

Common Mistakes:

• Assuming unset variables print empty strings
• Thinking script ignores unset variables
• Confusing literal printing with variable substitution

4. Given this script snippet with set -u enabled, what is the error and how to fix it?

#!/bin/bash
set -u

if [ "$USER_NAME" = "admin" ]; then
  echo "Welcome admin"
fi

medium

A. Error: Syntax error in if statement; fix by adding spaces

B. Error: USER_NAME undefined; fix by setting USER_NAME or using ${USER_NAME:-default}

C. No error; script runs fine

D. Error: Missing quotes around USER_NAME; fix by adding quotes

Solution

1. Step 1: Identify the cause of error with set -u

   The variable USER_NAME is used but not set, causing the script to stop with an error.

2. Step 2: Fix the error by providing a default value

   Use ${USER_NAME:-default} to avoid error if USER_NAME is unset, or ensure it is set before use.

3. Final Answer:

   Error: USER_NAME undefined; fix by setting USER_NAME or using ${USER_NAME:-default} -> Option B

4. Quick Check:

   Unset variable error fixed by default value [OK]

Hint: Use ${VAR:-default} to avoid unset variable errors [OK]

Common Mistakes:

• Ignoring that variable might be unset
• Trying to fix syntax instead of variable usage
• Forgetting to quote variables properly

5. How can you safely use a variable CONFIG_PATH in a script with set -u enabled, providing a default path if it is not set?

hard

A. Use echo "${CONFIG_PATH:-/etc/default/config}"

B. Use if [ -z "$CONFIG_PATH" ]; then echo "/etc/default/config"; fi

C. Disable set -u before using the variable

D. Use echo "$CONFIG_PATH" directly

Solution

1. Step 1: Understand default value syntax

   Using ${CONFIG_PATH:-/etc/default/config} provides a default if CONFIG_PATH is unset, avoiding errors with set -u.

2. Step 2: Compare other options

   Direct use causes error if unset, disabling set -u is not recommended, and the if statement does not print the variable if set.

3. Final Answer:

   Use echo "${CONFIG_PATH:-/etc/default/config}" -> Option A

4. Quick Check:

   Default value syntax avoids unset errors [OK]

Hint: Use ${VAR:-default} to safely handle unset variables [OK]

Common Mistakes:

• Using variable directly without default
• Disabling set -u instead of fixing code
• Incorrect if condition that skips printing variable