Stack overflow caused by recursive function

by

Whenever you call a function, including recursively, the return address and often the arguments are pushed onto the call stack. The stack is finite, so if the recursion is too deep you’ll eventually run out of stack space.

What surprises me is that it only takes 4793 calls on your machine to overflow the stack. This is a pretty small stack. By way of comparison, running the same code on my computer requires ~100x as many calls before the program crashes.

The size of the stack is configurable. On Unix, the command is ulimit -s.

Given that the function is tail-recursive, some compilers might be able to optimize the recursive call away by turning it into a jump. Some compilers might take your example even further: when asked for maximum optimizations, gcc 4.7.2 transforms the entire function into:

int returnZero(int anyNumber) {
  return 0;
}

This requires exactly two assembly instructions:

_returnZero:
        xorl    %eax, %eax
        ret

Pretty neat.

More Related Contents:

  1. does cout before return statement of recursive function stops it?
  2. how can i increase the speed of my C++ calculation [closed]
  3. Optimization code for a debug function (c++11 with templates) [closed]
  4. C++ Creating a parking charge
  5. Possibilities to quit a function
  6. Why pass by const reference instead of by value?
  7. Overload a C++ function according to the return value
  8. How to convert a lambda to an std::function using templates
  9. Is it legal to recurse into main() in C++? [duplicate]
  10. Meaning of = delete after function declaration
  11. Why is std::function not equality comparable?
  12. Which is more efficient: Return a value vs. Pass by reference?
  13. Why does C++ allow unnamed function parameters?
  14. Is this infinite recursion UB?
  15. Understanding Recursion to generate permutations
  16. Inferring the call signature of a lambda or arbitrary callable for “make_function”
  17. Why use a const member function?
  18. Declare variables at top of function or in separate scopes?
  19. Is there any way a C/C++ program can crash before main()?
  20. Why I can access member functions even after the object was deleted?
  21. Calling a function in main
  22. C++ Function Callbacks: Cannot convert from a member function to a function signature
  23. Pointer to array of unspecified size “(*p)[]” illegal in C++ but legal in C
  24. About Pointers To Functions in function declarations
  25. Why the initializer of std::function has to be CopyConstructible?
  26. Why am I able to make a function call using an invalid class pointer
  27. Recursion in c++ Factorial Program
  28. Pointing to a function that is a class member – GLFW setKeycallback
  29. Can I treat a specific warning as an error?
  30. Why can’t C++11 move a noncopyable functor to a std::function?

Leave a Comment