Replies: 2 comments
-
Will try the following approach: https://github.com/neovim/neovim/tree/master/src/nvim#tui-debugging-with-gdblldb Somehow couldn't find these instructions previously. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please read the checklist items before marking them as done and submitting (I have unchecked the offending ones for you). Rustaceanvim doesn't implement autocompletion. All I can do to help is recommend you follow the troubleshooting guide: Closing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checked other resources
:h rustaceanvim
.Description
Crash happens
Crash happens rarely when I try to complete autocomplete suggestion of some type (Rust/rustaceanvim) and type autocompletion would both complete type and add import statement at the top of the file.
I can not find in nvim log or LSP log any relevant error/warning.
Trying to debug
Neovim crashes with exit code 0213 (from octal -> 139) . Looks like SIGSEGV.
When I run neovim with gdb. I added break on exit syscall.
From backtrace found out that exit syscall is called from Event handler in
https://github.com/neovim/neovim/blob/master/src/nvim/event/proc.c
Which is called from event processed in main loop (nvim multiqueue.c).
I was expecting that neovim simply crashes, but instead it exits gracefully and I was expecting some kind of information why neovim decided to exit.
How to debug from where the event is raised and why nvim crashes.
Thank you for your help!
Example Code
Neovim version (nvim -v)
0.12.0dev and 0.11 stable
Operating system/version
Ubuntu 24.04.2
Output of :checkhealth rustaceanvim
Beta Was this translation helpful? Give feedback.
All reactions