Answer

In the C language, variables with automatic storage duration (auto, by default) are created on the stack when entering their scope (usually a function) and are automatically destroyed upon exiting it.

The features include:

• Access to such a variable is only possible within the block where it is declared.
• The stack has a limited size; overflowing it leads to a crash (stack overflow).
• Returning the address of an automatic variable from a function leads to undefined behavior.

Example of correct and incorrect usage:

int* wrong() {
    int x = 42;
    return &x;  // ERROR: x will be destroyed after exiting the function
}

void correct() {
    int y = 123;
    printf("%d\n", y); // all good
}

---

Trick Question

What happens if you return the address of a local variable from a function?

Common incorrect answer: "The pointer will preserve its value."

Correct answer: The returned address will become invalid after exiting the function, and the memory area will be reassigned to other automatic variables or functions. Using such a pointer leads to undefined behavior.

Example:

int* myfunc() {
    int temp = 10;
    return &temp; // temp will be destroyed after return
}

int main() {
    int* p = myfunc();
    printf("%d\n", *p); // UNDEFINED BEHAVIOR
}

---

Examples of real errors due to ignorance of the topic's subtleties

---

Story

In a large banking system project, a programmer returned a pointer to a local array from a user-defined function to process results. The system was unstable: data was periodically corrupted or unexpectedly changed, leading to an expensive bug in reporting.

Story

In the code for a peripheral device driver, a programmer used a stack buffer for asynchronous transmission. The delay between the start and completion of transmission led to data corruption as the buffer was destroyed before the operation completed.

Story

In the firmware of a medical recorder, caching was implemented on the stack to speed up data processing. Under load, the stack overflowed, causing device resets and loss of patient data.