Closed pedrohms closed 9 months ago
Given that neither nvim-dap nor nvim-jdtls do anything with ffi this sounds more like a neovim bug.
please report it there but make sure to provide the information requested in the issue template. Without a crash dump the issue will likely get closed
Tank you for the answer @mfussenegger. Just for future references, how can I get this crash dump from neovim ? Im kinda new in nvim
Tank you for the answer @mfussenegger. Just for future references, how can I get this crash dump from neovim ? Im kinda new in nvim
LSP client configuration
Current configuration:
Eclipse.jdt.ls version
1.28
Steps to Reproduce
Im using the mason jdtls installation from java-debug-adapter. It happend in any project I created
Expected Result
neovim crashs with message on somewhere on the screen. The messages can change to "free(): invalid next size (fast)" or "munmap_chunk(): invalid pointer" or another I cant remmber relative to pointer.
Actual Result
No logs