Closed ibsil closed 4 months ago
I reproduce the issue, gdb shows rollout code as 1.
I can also confirm that I have this same issue. Not using nvim-dap-ui.
gcc (GCC) 13.2.1 20240417
Python 3.12.3
pynvim 0.5.0
Sounds like a duplicate of https://github.com/mfussenegger/nvim-dap/issues/1150 ?
Note that the error is printed when the debug session exits, and it stops fine at breakpoints and so on.
@mfussenegger You are right. Thanks for answering.
You can disregard my comment since I was using a non supported version of gcc (13.2) and was not getting breakpoints which I wrongly correlated with the above message. I updated to gcc 14.1 today and it is indeed hitting breakpoints and the message printed is after the session exits as you stated.
Changed the process shutdown logic a bit (https://github.com/mfussenegger/nvim-dap/pull/1210). It now closes the stdio handles after the process has exited, instead of doing that a bit earlier. That gets rid of the error messages in the repl.
Thanks @mfussenegger I have confirmed the fix.
Debug adapter definition and debug configuration
I have installed nvim-dap, and nvim-dap-ui and GDB 14.2 which should have DAP included. I have also written a simple C program
main.c
for testing that nvim-dap is working as expected.In my
init.lua
I have written the dap configuration as follows:The program
main.c
compiles and runs without issue.Debug adapter version
No response
Steps to Reproduce
main.c
withgcc -ggdb main.c -o main
main.c
and call:DapContinue
, specify path to executablemain
:DapToggleRepl
Expected Result
Expected dap-ui to bring up windows used to aid in debugging the program (program state, function call stack, expression watching, breakpoints, etc.)
Actual Result