Stop debuging process about wxdap HOT 3 CLOSED

Here is fine. I don't mind discussions here

I usually prefer the m_client.Reset() since I don't really want to rely on an external implementation to implement this for me, consider the option that the process might crash or fail to follow the protocol to the letter?

In my implementation within CodeLite, I handle all cases like this:

• OnDapLaunchResponse with success == false I call to an internal method DoCleanup()
• OnDebugStop() - when user clicks the Stop button, I call to DoCleanup()
• OnDapExited - same, I call DoCleanup()

DoCleanup() does the following:

• Removes the debugger marker from the UI
• calls m_client.Reset()
• Terminates the dap server (codelldb or lldb-vscode or whatever)

Some notes and observations from testing it against 2 servers:

You should note that I am testing the demo against two dap-servers: codelldb and lldb-vscode (my personal favorite)
There are problems, but in general, lldb-vscode (from the LLVM team, the people how wrote clang and clangd) seems the better and more reliable to me

There is an issue with setting breakpoints, you can add function breakpoint (click on the new button I added to the UI and type the function name). However, placing breakpoints with file:line format does not work reliably. It only works when passing relative file path (e.g main.cpp instead of C:\src\main.cpp) - this looks like a bug to me (lldb-vscode can handle full paths, but it requires some strange format like /Users/eran/src/main.cpp instead of native format like C:\Users\eran\src\main.cpp)

from wxdap.

Thanks very much for the post.
I found some issues with the codelldb and now that I have started to use lldb-vscode I have found it to be more reliable.

I have just started to add breakpoint support and have to modify the code to make the path relative as I am using the GDB/MI code as a starting point.

The lldb-vscode path looks like a CygWin path and I had to do this conversion last year when I updated the Cygwin debugging support to work in C::B. If you look in the https://github.com/acotty/CodeBlocks_Unofficial_Testing/blob/master/src/sdk/cygwin.cpp file and look at the GetCygwinPath() function that I did to make the conversion. Unfortunately I used the Cygwin cygpath.exe so it will not work, but will give you some pointers if you do want to eventually use lldb-vscode.

from wxdap.

I have breakpoint working (no s) as the existing code sets one breakpoint in a file at a time and needs to be refactored.

from wxdap.