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

Build fails when using enable sanitizers script #10482

Closed
borrrden opened this issue Jun 9, 2018 · 3 comments
Closed

Build fails when using enable sanitizers script #10482

borrrden opened this issue Jun 9, 2018 · 3 comments
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity

Comments

@borrrden
Copy link

borrrden commented Jun 9, 2018

Disclaimer: The reason I am trying to do this is so I can run an ASAN enabled native library that I heavily use with P/Invoke. However it seems if I don't compile coreclr with the same ASAN enabled the arguments from C# get turned into garbage on their way into C++. If this should not the case, then please inform me.

Building against the v2.1.0 tag

I'm running following the instructions I found here verbatim in an ubuntu:14.04 docker container. The build succeeds using build.sh debug skiptests clang3.9 but then when I run . enablesanitizers.sh asan clang3.9 the same build invocation fails with the following:

/usr/bin/ld: /usr/lib/llvm-3.9/bin/../lib/clang/3.9.1/lib/linux/libclang_rt.asan-x86_64.a(asan_allocator.cc.o): unrecognized relocation (0x2a) in section `.text'
/usr/bin/ld: final link failed: Bad value
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [src/coreclr/hosts/unixcorerun/corerun] Error 1
make[1]: *** [src/coreclr/hosts/unixcorerun/CMakeFiles/corerun.dir/all] Error 2

(Similar error for coreconsole)

@borrrden
Copy link
Author

borrrden commented Jun 9, 2018

Ubuntu 18 works so maybe Ubuntu 14's ld is too old.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels May 12, 2024
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone May 26, 2024
Infrastructure Backlog automation moved this from Future to Closed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity
Projects
Status: Done
Development

No branches or pull requests

2 participants