Evan Martin

``` $ export RUST_LOG=trace $ target/debug/retrowin32 --win32-trace '*' --debugger exe/winapi/winapi.exe INFO win32/src/winapi/kernel32/dll.rs:173 kernel32/dll/LoadLibraryA(filename:Some("kernel32.dll")) INFO cli/src/debugger.rs:125 Waiting for a GDB connection on "localhost:9001"... INFO cli/src/debugger.rs:128 Debugger connected from [::1]:60810 ^C ```...

In case it's helpful, in the hung state it's attempting to read here ``` frame #7: 0x000000010001107c retrowin32`gdbstub::stub::GdbStub$LT$T$C$C$GT$::run_blocking::ha03ebcdac8d4acf5(self=, target=0x000000016fdfd5e8) at mod.rs:170:32 167 gdb = match gdb { 168 state_machine::GdbStubStateMachine::Idle(mut gdb)...

I'm using an in-tree simple logger, which doesn't have any configuration, all my logs are enabled. But it's blocked within gdbstub so I don't expect any of those logs. Is...

I thought to try gdb but: ``` $ brew install gdb gdb: The x86_64 architecture is required for this software. ``` But I just discovered there are arm builds of...

Ah, I think what I was missing is that gdbstub using the log crate requires my executable to provide some hooks for it to log anything. I will investigate that...

Startup, using the same lldb script as above: ``` INFO cli/src/debugger.rs:125 Waiting for a GDB connection on "localhost:9001"... INFO cli/src/debugger.rs:128 Debugger connected from [::1]:62746 TRACE gdbstub-0.7.1/src/protocol/recv_packet.rs:59

Dug a bit in the llvm github repo (the search is broken, yuck) and found I think [the relevant code](https://github.com/llvm/llvm-project/blob/2582d11f1a8a5783828156d3ced354727f422885/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp#L2624C22-L2624C32)

I looked into this a little more. For reasons not clear to me it appears lldb expects there to be an additional process in the mix. See discussion of 'debugserver'...

I also was misled by the LLDB code in this repo, given that this is lldb straight out of the box without configuration. Their docs mention: > In order to...

Sorry to keep updating this, but I figure it will be helpful for you in case someone else shows up with my questions: I was using the lldb command `platform...