Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teach bb-install.mk to pick up special jlls for msan #46418

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

Keno
Copy link
Member

@Keno Keno commented Aug 19, 2022

Verified working by setting SANITIZE_MEMORY=1 and then checking:

$ nm -D usr/lib/libstdc++.so | grep msan
                 U __msan_init
                 U __msan_memcpy
                 U __msan_memmove
                 U __msan_memset
                 U __msan_param_tls
                 U __msan_retval_tls
                 U __msan_va_arg_overflow_size_tls
                 U __msan_va_arg_tls
                 U __msan_warning_with_origin_noreturn

Verified working by setting `SANITIZE_MEMORY=1` and then checking:
```
$ nm -D usr/lib/libstdc++.so | grep msan
                 U __msan_init
                 U __msan_memcpy
                 U __msan_memmove
                 U __msan_memset
                 U __msan_param_tls
                 U __msan_retval_tls
                 U __msan_va_arg_overflow_size_tls
                 U __msan_va_arg_tls
                 U __msan_warning_with_origin_noreturn
```
Copy link
Sponsor Member

@vtjnash vtjnash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. But we might need to figure out how to add these to refresh_checksums, so they don't get deleted (or ignored) the next time someone tries to update this dep

@fingolfin
Copy link
Contributor

This was approved but never merged, and assigned to @gbaraldi who some time later opened a new PR #47420 with identical title to this one... So maybe this PR here should be closed in favor of the other? Or what is the status / relation? Or maybe this PR here is just a small step towards the more extensive work in #47420, and could / should be merged already now?!

@gbaraldi
Copy link
Member

Yeah that second one was the one that got closer, but still had some issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants