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
Following a recent discussion with a user Vector35/binaryninja-api#5833, I learned that the LLDB 18.1 actually supports Windows remote debugging (from macOS/Linux). This is a great improvement and may server as a solution to #70.
However, despite the setup seems to be working to some degree, there are also fatal blockers: llvm/llvm-project#60063. We should see if we can submit a patch to fix the underlying issue and get remote Windows debugging support
The text was updated successfully, but these errors were encountered:
I see nothing weird when using the debugger GUI. I switched between disassembly and other IL types, and tried bv.read and it looks normal.
That is interesting, on my end I am seeing the byte of the breakpoint being reported as 0xcc. Could you please let me know how you are doing the debugging so that I can see if there are any important differences
Following a recent discussion with a user Vector35/binaryninja-api#5833, I learned that the LLDB 18.1 actually supports Windows remote debugging (from macOS/Linux). This is a great improvement and may server as a solution to #70.
However, despite the setup seems to be working to some degree, there are also fatal blockers: llvm/llvm-project#60063. We should see if we can submit a patch to fix the underlying issue and get remote Windows debugging support
The text was updated successfully, but these errors were encountered: