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
As of right now test_memory_leaks.py only looks for leaks involving successful function calls. Where possible, it should also explicitly cause an error condition in the tested C function (mainly we want to make sure all resources which are typically freed in the "error:" gotos are executed).
The text was updated successfully, but these errors were encountered:
As of right now test_memory_leaks.py only looks for leaks involving successful function calls. Where possible, it should also explicitly cause an error condition in the tested C function (mainly we want to make sure all resources which are typically freed in the "error:" gotos are executed).
The text was updated successfully, but these errors were encountered: