Call stack behavior in C++ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the call stack in C++?

The call stack is a special area in memory that stores information about active functions or methods. It keeps track of where each function should return after it finishes.

beginner

What happens when a function is called in terms of the call stack?

When a function is called, a new stack frame is created and pushed onto the call stack. This frame holds the function's parameters, local variables, and return address.

intermediate

Explain what a stack frame contains.

A stack frame contains the function's parameters, local variables, and the return address to know where to continue after the function finishes.

beginner

What happens to the call stack when a function returns?

When a function returns, its stack frame is popped off the call stack, and the program continues execution from the return address stored in the previous stack frame.

intermediate

What is a stack overflow and when can it happen?

A stack overflow happens when the call stack grows beyond its limit, usually because of too many nested function calls or infinite recursion, causing the program to crash.

What does the call stack store when a function is called?

A Only the function's name

B Global variables only

C The entire program's code

D The function's parameters, local variables, and return address

The call stack stores the function's parameters, local variables, and return address in a stack frame.

What happens to the call stack when a function finishes execution?

A The current stack frame is popped

B A new stack frame is pushed

C The stack is cleared completely

D Nothing changes

When a function finishes, its stack frame is popped off the call stack.

Which of these can cause a stack overflow?

A Declaring local variables

B Too many nested function calls

C Using global variables

D Calling functions once

Too many nested function calls or infinite recursion can cause the call stack to overflow.

Where does the program continue after a function returns?

A At a random memory location

B At the start of the program

C At the return address stored in the previous stack frame

D At the end of the program

The program continues at the return address stored in the previous stack frame.

What is NOT stored in a stack frame?

A Global variables

B Function parameters

C Return address

D Local variables

Global variables are stored in a different memory area, not in the stack frame.

Describe the lifecycle of a function call in terms of the call stack.

Think about what happens when you call a function and when it finishes.

Explain what causes a stack overflow and how it relates to the call stack.

Imagine calling functions inside functions without stopping.