What information is usually stored in the call stack during program execution?

The call stack during program execution typically stores the following information:

• Return address — where to return after the current function finishes.
• Local variables of the current function.
• Function parameters.
• Execution context (e.g., pointer to the current stack frame).

The call stack organizes the sequence of function calls, allowing the program to correctly return to previous calls after completing the current ones. This is important for tracking execution order and managing memory for local data.

For example, when calling function A, which calls function B, the stack will initially contain frame A, then frame B will be added. After B finishes, control returns to A, and frame B is removed from the stack.