Hello.

Just why edi ok with test, but not when attempt ?

Forgot to remove debug strings ^^ and also printf debug ^^

Yes, indeed

Runtime per se won't be a problem here (maybe it is about 0.4ms). The real trouble is, that this ends up in an infinite loop for values above the square closest to INT_MAX.

Nice !

But what about big numbers, according compute time (eg: 2147395600 or 2147483647)

Hello siebenschlaefer,

is using
a locally allocated char array
which is returned via strdup(charray)
a form of memory leak?

thank you,
rowcased

Hello.

Mybe i already saw that somewhere many many time ago, but i prefer tell i didn't know that function.
In my first answer, i made the wheel again, almost ^^.

Thanks to have been learnt me that function.

• char *variablename[size]; defines variablename to be an array of char *, not of char.
• The task imposes no restrictions on the size of list, so any fixed size thestring might be too small.
• On machines with 32 bit integers MIN_INT is -2147483648, so dummystr should be able to take 16 characters (11 for the int, 4 for " -> " and 1 for the terminating '\0').
• thestring has automatic storage duration (i.e. resides on the stack), its lifetime ends when the execution of stringify ends. return thestring returns a pointer to that array, resulting in undefined behaviour.

Yes, this function allocates some memory and the caller is reposible for deallocation. That's common in C programs.
All alternatives either leak memory, cannot handle arbitrarily large results, and/or are not thread safe or reentrant.

Hello.

What about the memory.
malloc allocated memory, but never released, isn't it ?

Hello all.

My, i didn't think about ... THAT !!!
Of course !!!

Thank you very much for this hint !!! I should read more carrefully next time !!!