U++ forum: Welcome to the forum

Re: MemorySanitizer: use-of-uninitialized-value in CoWork [message #52110 is a reply to message #52109]

Sat, 20 July 2019 08:56

mirek
Messages: 13975
Registered: November 2005

Ultimate Member

Novo wrote on Sat, 20 July 2019 01:27

mirek wrote on Fri, 19 July 2019 17:50
This really feels like sanitizer bug, but whatever....

Thanks!

I do not think this is a bug. A team working on sanitizers is exceptionally good.
MemorySanitizer reports all uninitialized memory reads, including, for example, memmove and memcpy of uninitialized memory. This is not necessarily a bug, but this allows the sanitizer to be fast unlike valgrind.
The problem is that all sanitizers exit app on first detected error.

Well, but obviously we are not doing anything bad here. So it must be either a bug in sanitizer or in standard library (or perhaps in compiler).

Mirek

Report message to a moderator