We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey,
When attempting to use crystalline it gets killed pretty quickly after being loaded by vim.
(lldb) target create "crystalline" --core "crystalline.core" Core file '/home/llua/src/exercism/crystal/armstrong-numbers/crystalline.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'GC-marker-2', stop reason = signal SIGSEGV * frame #0: 0x0000000807e6b537 libgc-threaded.so.1`GC_mark_from + 823 frame #1: 0x0000000807e6bcda libgc-threaded.so.1`___lldb_unnamed_symbol830 + 426 frame #2: 0x0000000807e6bb06 libgc-threaded.so.1`GC_help_marker + 118 frame #3: 0x0000000807e744ed libgc-threaded.so.1`___lldb_unnamed_symbol862 + 317 frame #4: 0x0000000807ecb83a libthr.so.3`___lldb_unnamed_symbol556 + 314
Using gui
0x0000000807e6b537 │◆movq 0x10(%rax), %rbx
in libgc-threaded.so.1`GC_mark_from seems to be the point at which causes it.
libgc-threaded.so.1`GC_mark_from
i was using vim-lsp with vim 9.0.1366
vim-lsp
9.0.1366
if executable('crystalline') au User lsp_setup call lsp#register_server({ \ 'name': 'crystalline', \ 'cmd': {server_info->['crystalline','--stdio']}, \ 'allowlist': ['crystal'], \ }) endif
along with
The text was updated successfully, but these errors were encountered:
Hey @llua,
Sorry but I will not be able to debug that on my own, I do not have access to a freebsd environment.
Sorry, something went wrong.
No branches or pull requests
Hey,
When attempting to use crystalline it gets killed pretty quickly after being loaded by vim.
Using gui
in
libgc-threaded.so.1`GC_mark_from
seems to be the point at which causes it.i was using
vim-lsp
with vim9.0.1366
along with
The text was updated successfully, but these errors were encountered: