C – function returning a pointer to a local variable

by

Every time you call abc it “marks” a region at the top of the stack as the place where it will write all of its local variables. It does that by moving the pointer that indicates where the top of stack is. That region is called the stack frame. When the function returns, it indicates that it does not want to use that region anymore by moving the stack pointer to where it was originally. As a result, if you call other functions afterwards, they will reuse that region of the stack for their own purposes. But in your case, you haven’t called any other functions yet. So that region of the stack is left in the same state.

All the above explain the behavior of your code. It is not necessary that all C compilers implement functions that way and therefore you should not rely on that behavior.

More Related Contents:

  1. function returns address of local variable, but it still compile in c, why?
  2. Given the state of the stack and registers, can we predict the outcome of printf’s undefined behavior
  3. Why are these constructs using pre and post-increment undefined behavior?
  4. (Why) is using an uninitialized variable undefined behavior?
  5. Is the “struct hack” technically undefined behavior?
  6. Is a^a or a-a undefined behaviour if a is not initialized?
  7. Is accessing a global array outside its bound undefined behavior?
  8. Is the behaviour of casting a negative double to unsigned int defined in the C standard? Different behaviour on ARM vs. x86
  9. A question about union in C – store as one type and read as another – is it implementation defined?
  10. When is casting between pointer types not undefined behavior in C?
  11. What is Undefined Behaviour in C? [duplicate]
  12. 32 bit unsigned multiply on 64 bit causing undefined behavior?
  13. In C99, is f()+g() undefined or merely unspecified?
  14. Unspecified, undefined and implementation defined behavior WIKI for C
  15. Why does this implementation of strlen() work?
  16. Sequence points and side effects in C
  17. Why does char* cause undefined behaviour while char[] doesn’t?
  18. Is this undefined C behaviour?
  19. Why does a program accessing illegal pointer to pointer not crash?
  20. Is while(1); undefined behavior in C?
  21. Does C have an equivalent of std::less from C++?
  22. C code with undefined results, compiler generates invalid code (with -O3)
  23. printf() with no arguments in C compiles fine. how?
  24. When is it valid to access a pointer to a “dead” object?
  25. Is it Undefined Behaviour to cast away the constness of a function parameter?
  26. Why is undefined behaviour allowed in C
  27. Cast T[][] to T*
  28. Turbo C++: Why does printf print expected values, when no variables are passed to it?
  29. 2D Array indexing – undefined behavior?
  30. Uninitialized variable in C [duplicate]

Leave a Comment