Issue #3378
Checking memory safety in make check on Windows
Description
We have observed that sometimes some checks on Windows fail with segfaults. Primarily the TLS related ones.
I'd like to automate checking the memory safety of failing checks within the CI. As valgrind doesn't run natively on Windows, an alternative has to be found.
I looked at Dr.Memory and it seems to be usable.
Do you have any experience with trying to set that up? And what's the best way to implement this into the test suites?
History
#1 Updated by Tobias Brunner 2 months ago
- Category set to windows
- Status changed from New to Feedback
We have observed that sometimes some checks on Windows fail with segfaults. Primarily the TLS related ones.
Yep, those or the multi-threading ones. Reason, no idea whatsoever? (But it's Windows, so...)
Do you have any experience with trying to set that up?
Nope.
And what's the best way to implement this into the test suites?
No idea.
#2 Updated by Noel Kuntze 2 months ago
- Status changed from Feedback to Closed
I see. So down the rabbit hole I go. :)
Thank you!
#3 Updated by Noel Kuntze 2 months ago
- Resolution set to No change required