Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Invalid memory access (signal 11) #4391
I recently ported a haste-client from ruby to crystal.
Operation System: Solus OS, Kernel 4.9.26
When trying to compile the haste-client it gives this output:
The same with this:
i can successfully compile it with the following commands:
It seems that adding
oh, by the way it compiles with
@ysbaddaden i have just noticed that my installed LLVM version is 3.9.1 but
I tried to compile crystal as described in the docs. (with additional git checkout tags/0.22.0)
I made a hello world test file, with this code:
I tried to compile it and it works normally. With
But compiling my haste-client works only without
About the --release issue: it would seem the issue isn't related to the LLVM version, thanks for testing. Now we have another bug
About the host target, this is part a Solus issue, part a Crystal issue.
The Solus issue is that the
The triple is missing an actual ABI (libc) to target. Assuming the libc is glibc, it should be
The Crystal issue is that we use pre-generated libc bindings. Ideally we should generate them automatically from C headers. That would avoid the issue, but it's more complicated to put in place and would require more libraries (i.e.
Yes, Solus OS uses glibc.
Maybe create a symlink instead of copying, so pulling a new Crystal version will automatically update the libc (it might change), but I guess it doesn't matter much since the next release should be compiled with LLVM 3.8.1
Closing, since this is an LLVM issue...