Paulo Antonio Alvarez 89ea0e10d8 Return values saved in history ...

On some contexts, we need to call one function to free some resource
allocated by another function based on the return value of the second
function. For example, every time pthread_mutex_trylock suceeds, you
need to unlock it, and only in those cases. While this could be done
with the return value sequence, it does not really work for a sequence
of custom fakes. Now we save the return values in the member
return_val_history, which works pretty much like arg_history, only
for the return values.

2017-08-15 23:36:49 -03:00

17 KiB

Raw Blame History

View Raw