You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nvim-gdb becomes completely unresponsive to user input. The terminal window shows the standard message checkpoint 1: fork returned pid <pid>, but gdb prompt doesn't appear after that, it is impossible to enter CLI commands anymore, and nvim-gdb commands (GdbNext, GdbStep...) do nothing. After closing nvim, gdb process is still running until force killed. It doesn't always happen, but most of the times.
What were you expecting to happen?
A checkpoint should be created, and nvim-gdb should continue to receive user input.
I've just found out that this is only reproducible with gdb 15.1, which is the default version in the Arch repos at the moment. But downgrading to 14.2 solves the problem completely. Just to illustrate the issue, this is gdb 15.1, also reproducible with clean nvim config (test/nvim.py).
What are the steps to reproduce this issue?
What happens?
Nvim-gdb becomes completely unresponsive to user input. The terminal window shows the standard message
checkpoint 1: fork returned pid <pid>
, but gdb prompt doesn't appear after that, it is impossible to enter CLI commands anymore, and nvim-gdb commands (GdbNext, GdbStep...) do nothing. After closing nvim, gdb process is still running until force killed. It doesn't always happen, but most of the times.What were you expecting to happen?
A checkpoint should be created, and nvim-gdb should continue to receive user input.
Any logs, error output, etc?
https://gist.github.com/Alexey104/7812486bb2f6df77140f3c7b5bce52de
The text was updated successfully, but these errors were encountered: