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

[LLVM] #9966

Open
Muttiskitten opened this issue Oct 25, 2024 · 1 comment
Open

[LLVM] #9966

Muttiskitten opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels

Comments

@Muttiskitten
Copy link

Describe GraalVM and your environment :

  • GraalVM version or commit id if built from source: [e.g. 19.3]
  • CE or EE: [e.g.: CE]
  • JDK version: [e.g.: JDK8]
  • OS and OS Version: [e.g.: macOS Catalina]
  • Architecture: [e.g.: amd64]
  • The output of java -Xinternalversion:
 A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000076d802806ecf, pid=98760, tid=98829
#
# JRE version: OpenJDK Runtime Environment GraalVM CE 23.0.1+11.1 (23.0.1+11) (build 23.0.1+11-jvmci-b01)
# Java VM: OpenJDK 64-Bit Server VM GraalVM CE 23.0.1+11.1 (23.0.1+11-jvmci-b01, mixed mode, sharing, tiered, jvmci, jvmci compiler, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [spark-4eda12cd5e94-libasyncProfiler.so.tmp+0x6ecf]  NMethod::isNMethod()+0x1f
#
# Core dump will be written. Default location: /home/mrkitten/roguecraft/1.21/core
#
# An error report file with more information is saved as:
# /home/mrkitten/roguecraft/1.21/hs_err_pid98760.log
[81.315s][warning][os] Loading hsdis library failed

Have you verified this issue still happens when using the latest snapshot?
You can find snapshot builds here: https://github.com/graalvm/graalvm-ce-dev-builds/releases

Describe the issue
A clear and concise description of the issue.

How to compile the LLVM bitcode that causes the problem

  • Did you use the bundled llvm toolchain for compiling to LLVM bicode (see lli --print-toolchain-path)?
  • If not, does problem still occur when using the toolchain?
  • If the toolchain cannot be used, which compilers/tools were use and what versions (e.g., clang --version)?

Code snippet or code repository that reproduces the problem

Steps to reproduce the problem
Please include both build steps as well as run steps

  1. Step one [e.g.: $LLVM_TOOLCHAIN/clang mytest.c -o mytest]
  2. Step two [e.g.: $GRAAALVM_HOME/bin/lli mytest]

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

@oubidar-Abderrahim
Copy link
Member

Please share a reproducer and clear steps on how to reproduce this issue, thank you

@oubidar-Abderrahim oubidar-Abderrahim self-assigned this Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants