Hi Marko,
Uninstrumented code under ASan leads to false negatives. Under MSan,
uninstrumented code leads to false positives. MSan is thus not suitable to
be used as a preloaded DSO.
If you're really, really, extremely dedicated and willing to annotate
<https://clang.llvm.org/docs/MemorySanitizer.html#blacklist> *every*
instance
where memory that's initialized in uninstrumented code flows to
instrumented code, then you might be able to find some bugs. But it's worth
bearing in mind that usage of MSan in this way is warranty-voiding.
On Wed, Apr 7, 2021 at 12:01 PM Marko Stanojlovic via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello llvm developers,
>
> Is there a way to use Memory Sanitizer when there is a third-party
> executable which cannot be recompiled,
> but it loads shared libraries that can be recompiled and we want to test
> them with MSan? In other words could be MSan used as dso?
> Similar to ASan usage described on its wiki page -
> https://github.com/google/sanitizers/wiki/AddressSanitizerAsDso.
>
> Kind regards and thanks in advance for response,
> Marko Stanojlović
>
> SYRMIA LLC @ Belgrade Office Park
> Djordja Stanojevica 12,
> Beograd 11070
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20210407/ebfb2ee1/attachment.html>