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
We'd like to run vagrind on Lind to check for any memory leaks. Let's try to do this.
One issue is that our fork memory copy relies on mremap() which isn't allowed with valgrind. We can create and option to fallback to a straight memcpy the memory regions between cages on fork instead of the current setup and just enable that version when running valgrind.
The text was updated successfully, but these errors were encountered:
We'd like to run vagrind on Lind to check for any memory leaks. Let's try to do this.
One issue is that our fork memory copy relies on mremap() which isn't allowed with valgrind. We can create and option to fallback to a straight memcpy the memory regions between cages on fork instead of the current setup and just enable that version when running valgrind.
The text was updated successfully, but these errors were encountered: