How is this respecting the "The returned string should be statically allocated and it won't be freed" requirement? The "true" and "false" here are declared on the stack on the function call, not on the heap and it will BE considered freed and eventually overwritten by some other process using the heap later down the road.
Although it "works" on the surface, returning strings like that will evenatually crash your programs.

Well, that was a 'clear problem' with he kata as when no instruction are executed, there should not be any SEGDEV error. Now if your assertion/testing code is doing a free operation without validation, I can't do nothing on that part as I didn't code it.

I started to get SEGDEV from testing.
So I commented everything in the function (because my code works under a real compiler) and I still get SEGDEV ??
I am starting to doubt the assertion code being used to valide our code.