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

vagrant: use LDFLAGS="-Wl,--no-as-needed" in sanitizer runs #255

Merged
merged 5 commits into from
May 15, 2020

Commits on May 15, 2020

  1. Configuration menu
    Copy the full SHA
    51a17d5 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    45538a3 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    bbae0d0 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    4097895 View commit details
    Browse the repository at this point in the history
  5. vagrant: use LDFLAGS="-Wl,--no-as-needed" in sanitizer runs

    Since version 10, both gcc and clang started to ignore certain linker errors
    when compiling with -fsanitize=address. This eventually leads up to -lcrypt
    not being correctly propagated, but the fact is masked by the aforementioned
    issue. However, when the binary attempts to load a symbol from the libcrypt
    binary, it crashes since it's not linked correctly against it.
    Negating the -Wl,--as-needed used by default by -Wl,--no-as-needed seems to
    help in this case.
    
    See:
      https://bugzilla.redhat.com/show_bug.cgi?id=1827338#c3
      systemd#247
    mrc0mmand committed May 15, 2020
    Configuration menu
    Copy the full SHA
    18b7044 View commit details
    Browse the repository at this point in the history