Update docs and compatablity matrix for debugging Windows PE running under wine with LLDB adapter

[rickhg12hs]

Many Windows PEs can run on Linux using wine. It would be useful and convenient if these Windows PEs could be debugged using Binary Ninja running on Linux.

[xusheng6]

I did some testing with the winedbg, and it appears to me that it even cannot work properly with GDB. Here are my findings:

1. To use winedbg, just run winedbg --gdb --port 31337 --no-start ./helloworld.exe, and then in GDB, run target remote localhost:31337 to connect to it
2. With GDB, we can connect to it normally, stepping and breakpoints also work fine initially . However, I tested with a helloworld.exe (https://github.com/Vector35/debugger/blob/dev/test/binaries/Windows-x86_64/helloworld.exe), and as soon as I step over a few times in the main function, the target just runs free and exits. I believe this is a winedbg bug. Until this is fixed, it would not be usable anyways
3. I tested with binja's LLDB adapter, and it is exactly the same as GDB, but slightly worse -- that the target runs free and exits immediately when I single step on the main function
4. With binja's GDB RSP adapter, I first had to fix a crash in Crash when using GDB RSP adapte to connect to winedbg due to wide registers #819. Then I realize the breakpoints do not work. I checked the packet capture and it appears winedbg does not support the Z0 packets to set breakpoints. It fails with 00 instead of OK. I checked how GDB is able to add breakpoints -- after Z0 fails, it writes to the memory contents directly to set the byte to 0xc3. I would say this is beyond the scope of the GDB RSP adapter, especially with Add a GDB machine interface adapter #170 in sight

Summary, nothing really works, and it is not my fault xD

[xusheng6]

Relevant packet for how GDB inserts the breakpoint after an attempted Z0 fails:

[xusheng6]

Outputs from winedbg and gdb when a failed debugging happen as mentioned in 2) above:

Winedbg:

winedbg --gdb --port 31337 --no-start ./helloworld.exe 
011c:0120: create process 'Z:\home\xusheng\debugger_build\debugger\test\binaries\Windows-x86_64\helloworld.exe'/0000000000000000 @0000000140001338 (0<0>)
011c:0120: create thread I @0000000140001338
target remote localhost:31337
011c:0120: loads DLL C:\windows\system32\ntdll.dll @00006FFFFFC50000 (3764224<5275>)
011c:0120: loads DLL C:\windows\system32\kernel32.dll @00006FFFFFA80000 (1798144<20938>)
011c:0120: loads DLL C:\windows\system32\kernelbase.dll @00006FFFFF470000 (6262784<15030>)
011c:0120: loads DLL C:\windows\system32\VCRUNTIME140.dll @00006FFFFC750000 (102400<774>)
011c:0120: loads DLL C:\windows\system32\ucrtbase.dll @00006FFFFEAE0000 (4141056<13071>)
011c:0120: loads DLL C:\windows\system32\tzres.dll @0000000180000000 (0<0>)
0000011c:00000120: unload DLL @0000000180000000
011c:0120: loads DLL C:\windows\system32\tzres.dll @0000000180000000 (0<0>)
0000011c:00000120: unload DLL @0000000180000000
0000011c:00000120: exit process (10)

GDB:

gdb ~/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe
GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git

Reading symbols from /home/xusheng/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe...
(No debugging symbols found in /home/xusheng/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe)
(gdb) target remote localhost:31337
Remote debugging using localhost:31337
warning: remote target does not support file transfer, attempting to access files from local filesystem.

0x00006fffffca59c1 in DbgBreakPoint () from /usr/lib/x86_64-linux-gnu/wine/x86_64-windows/ntdll.dll
(gdb) b *0x140001010
Breakpoint 1 at 0x140001010
(gdb) c
Continuing.

Breakpoint 1, 0x0000000140001010 in ?? () from /home/xusheng/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe
(gdb) ni
0x0000000140001015 in ?? () from /home/xusheng/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe
(gdb) 
0x000000014000101a in ?? () from /home/xusheng/debugger_build/debugger/test/binaries/Windows-x86_64/helloworld.exe
(gdb) 
[Inferior 1 (Remote target) exited with code 012]
(gdb)

[xusheng6]

Ok Upon further investigation, I found that:

1. binja's LLDB adapter works as good as GDB, albeit a little bit slower
2. The bug I ran into is very specific -- it only happens when stepping over at the start of the main function. If you either step into, or use a breakpoint to skip it, it works. So I guess this is a winedbg bug, but it does not really make the whole thing unusable

So I think winedbg is a usable setup with binja debugger. Will update the docs to reflect that later