Common pointer errors - Time & Space Complexity

Time Complexity: Common pointer errors

O(n)

Understanding Time Complexity

When working with pointers in C, it's important to see how mistakes can affect program speed.

We want to know how pointer errors impact the number of steps the program takes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void printArray(int *arr, int size) {
    for (int i = 0; i < size; i++) {
        printf("%d ", *(arr + i));
    }
}

int main() {
    int numbers[5] = {1, 2, 3, 4, 5};
    printArray(numbers, 5);
    return 0;
}
    

This code prints all elements of an integer array using a pointer.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the array elements using pointer arithmetic.
• How many times: The loop runs once for each element in the array (size times).

How Execution Grows With Input

As the array size grows, the number of steps grows in the same way.

Input Size (n)	Approx. Operations
10	10 steps
100	100 steps
1000	1000 steps

Pattern observation: The steps increase directly with the number of elements.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of items.

Common Mistake

[X] Wrong: "Using pointers always makes the code faster or simpler."

[OK] Correct: Pointer mistakes like wrong addresses or uninitialized pointers can cause errors or slow the program down, not speed it up.

Interview Connect

Understanding how pointer errors affect program steps helps you write safer, clearer code and shows you know how to think about program speed.

Self-Check

"What if we changed the pointer to point to a linked list instead of an array? How would the time complexity change?"

Practice

1. What is a common mistake when using pointers in C?

easy

A. Assigning a valid memory address to a pointer

B. Declaring pointers with the correct syntax

C. Using uninitialized pointers before assigning them an address

D. Using pointers to access array elements correctly

Solution

1. Step 1: Understand pointer initialization

   Pointers must be assigned a valid memory address before use to avoid undefined behavior.

2. Step 2: Identify common mistakes

   Using a pointer without initialization can cause crashes or unexpected results.

3. Final Answer:

   Using uninitialized pointers before assigning them an address -> Option C

4. Quick Check:

   Uninitialized pointer use = common error [OK]

Hint: Always initialize pointers before use to avoid errors [OK]

Common Mistakes:

• Dereferencing NULL pointers
• Forgetting to initialize pointers
• Confusing pointer and value assignment

2. Which of the following pointer declarations is syntactically correct in C?

easy

A. *int ptr;

B. int ptr*;

C. int &ptr;

D. int *ptr;

Solution

1. Step 1: Review pointer declaration syntax

   In C, the asterisk (*) goes between the type and the pointer name to declare a pointer.

2. Step 2: Check each option

   int *ptr; correctly declares a pointer to int. Options A, B, and D have invalid syntax.

3. Final Answer:

   int *ptr; -> Option D

4. Quick Check:

   Correct pointer syntax = int *ptr; [OK]

Hint: Pointer syntax: type *name; always asterisk before name [OK]

Common Mistakes:

• Placing * after variable name
• Using & instead of * for pointers
• Incorrect order of type and *

3. What will be the output of the following C code?

int x = 10;
int *p = &x;
*p = 20;
printf("%d", x);

medium

A. 10

B. 20

C. Garbage value

D. Compilation error

Solution

1. Step 1: Understand pointer assignment

   Pointer p points to variable x. Changing *p changes x's value.

2. Step 2: Trace the code execution

   *p = 20 sets x to 20. printf prints x, so output is 20.

3. Final Answer:

   20 -> Option B

4. Quick Check:

   Pointer dereference changes value = 20 [OK]

Hint: Changing *p changes the value pointed to [OK]

Common Mistakes:

• Confusing pointer address and value
• Expecting original value unchanged
• Ignoring pointer dereference effect

4. Identify the error in the following code snippet:

int *p;
*p = 5;
printf("%d", *p);

medium

A. Pointer p is not initialized before dereferencing

B. Syntax error in pointer declaration

C. Incorrect printf format specifier

D. No error, code runs fine

Solution

1. Step 1: Check pointer initialization

   Pointer p is declared but not assigned an address before use.

2. Step 2: Understand dereferencing consequences

   Dereferencing uninitialized pointer causes undefined behavior or crash.

3. Final Answer:

   Pointer p is not initialized before dereferencing -> Option A

4. Quick Check:

   Uninitialized pointer dereference = error [OK]

Hint: Always assign pointer before dereferencing [OK]

Common Mistakes:

• Assuming declaration initializes pointer
• Ignoring runtime crashes from bad pointers
• Misreading error as printf issue

5. Consider the code below. What is the safest way to avoid a common pointer error here?

int *p = NULL;
// Some code
printf("%d", *p);

hard

A. Check if p is NULL before dereferencing

B. Assign p to a random memory address

C. Remove the pointer and use an int variable instead

D. Ignore the NULL and dereference directly

Solution

1. Step 1: Understand NULL pointer risks

   Dereferencing NULL pointer causes runtime crash or undefined behavior.

2. Step 2: Apply safe pointer usage

   Always check if pointer is NULL before dereferencing to avoid errors.

3. Final Answer:

   Check if p is NULL before dereferencing -> Option A

4. Quick Check:

   NULL check before dereference = safe code [OK]

Hint: Always test pointer != NULL before use [OK]

Common Mistakes:

• Dereferencing NULL pointer causing crash
• Assigning invalid addresses
• Ignoring pointer safety checks