Question

I guarantee that this question has been asked before, but I haven’t been able to find it via search; sorry in advance for any redundancies.

It’s my (potentially wrong) understanding that you only allocate to the stack when you know the size of an object at compile time. So in the case of initializing an array, you could do one of these (and this should go on the stack):

char charArray[50];

Since the size of this array is known at compile time, this should have no issues.

On the other hand, this (I believe) is also valid code:

char anotherCharArray[someVariable + 50];

Would this go on the stack as well? I am pretty sure the code segfaults if you free() this, so it makes me think it does, but it doesn’t really make sense to me. Similarly, is the 100% sole situation where you have to use free() when the data was allocated via malloc?

Thanks in advance for your help.

Answer 1

Similarly, is the 100% sole situation where you have to use free() when the data was allocated via malloc?

Yes. (Apart from calloc and realloc, their return value is also to be free()‘d. Similarly, there are functions that use malloc() and this fact is documented, for example strdup() – the return value of these functions is also to be freed using free(), obviously.)

char anotherCharArray[someVariable + 50];

Would this go on the stack as well?

Yes, it does (in most implementations – of course, it’s not always true that you assume, but on most of the platforms, it is). And yes this is valid code, but it is only standard in C99.