You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It used to be valid to return the value 0 for a null pointer. I have no idea if this is due to the FREE-IT phrase or just a null pointer exception.
However it used to work. I fixed the issue by always return a real "ib-malloc'd" string. It would be better if the engine handled this more gracefully.
To be concise - here is the OLD c-code which I have used for a long time.
if (some-test) return 0;
The text was updated successfully, but these errors were encountered:
Submitted by: Ray Holme (rholme)
It used to be valid to return the value 0 for a null pointer. I have no idea if this is due to the FREE-IT phrase or just a null pointer exception.
However it used to work. I fixed the issue by always return a real "ib-malloc'd" string. It would be better if the engine handled this more gracefully.
To be concise - here is the OLD c-code which I have used for a long time.
if (some-test) return 0;
The text was updated successfully, but these errors were encountered: