Valgrind is a great way to diagnose memory-safety issues, but it doesn't like libco ve

Fixed by <a class="issue-link js-issue-link" data-error-text="Failed to load title" da

To be clear, <a class="issue-link js-issue-link" data-error-text="Failed to load title

Teach libco about valgrind about libco HOT 3 CLOSED

higan-emu commented on June 3, 2024 1

Teach libco about valgrind

from libco.

namandixit commented on June 3, 2024 2

This webpage contains some more details about making it work with various debuggers and sanitizers, in addition to Valgrind.

from libco.

zuiderkwast commented on June 3, 2024

Fixed by #39.

from libco.

Screwtapello commented on June 3, 2024

To be clear, #39 tells Valgrind about stacks when they are created.

it does not tell Valgrind about stacks when they are destroyed, but it doesn't seem to matter just yet
- If it does matter, we can figure something out
it does not add support for Address Sanitizer or Thread Sanitizer, because those tools don't report problems with our test apps

I'm calling this issue done, we can open new issues about specific issues if and when they occur.

from libco.