-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Segmentation fault in libbcc.so.0.3.0 (Fedora 26, bcc-0.3.0-2.fc26.x86_64, kernel 4.13.5-200.fc26.x86_64) #1402
Comments
Steps to reproduce:
(sudo is required to run ctest) |
Could you get a stack trace of the segfault? The message is not very helpful since it's virtual address of the dynamically loaded |
OK, I am just downloading about 1GB of debuginfo packages ... |
Stack trace:
|
Segfault occurs with bcc-0.3.0-2.fc26.x86_64 only! |
Fedora should update the bcc.fc26.x86_64 package |
I submitted a bug in Red Hat bugzilla for it: |
The bug is fixed in llvm 5.0. |
@yonghong-song, so is this bug in llvm? I have llvm v4.0.1 installed and the bug occurs with bcc-0.3.0-2.fc26.x86_64 but with current master (v0.3.0-408-gd2786b6) it does not, so upgrading bcc from bcc-0.3.0-2.fc26.x86_64 to v0.3.0-408-gd2786b6 fixes this issue ... |
Right. The bug is in llvm. |
Thanks |
! Segfault occurs with bcc-0.3.0-2.fc26.x86_64 only !
(with current master (v0.3.0-408-gd2786b6) it works well)
Output:
Message from dmesg:
The beginning of the generated code (
/virtual/main.c
) is the following:OS: Fedora 26
bcc: bcc-0.3.0-2.fc26.x86_64
kernel 4.13.5-200.fc26.x86_64
clang: clang-4.0.1-5.fc26.x86_64
llvm: llvm-4.0.1-1.fc26.x86_64
The text was updated successfully, but these errors were encountered: