wow. the GDB remote stub sure works in a way that I'm sure made sense to someone at some point
hmm. I've got three things: a program implementing a GDB stub, a python module to parse it, and a spec from the GDB documentation.
They do not agree, but I do not know enough about how this shit is SUPPOSED to work to tell which one is fucked.
I'm just gonna assume that someone compiled this code for the emulator and it has never worked. that'll let me keep more of my sanity.

can't find a breakpoint because the code that's encoding breakpoint values is encoding them into lowercase and the remote gdb stub is encoding them into uppercase.

so if the address of your address point has any hex digits, it'll fail.

because 80153ff8 != 80153FF8

COMPUTERS WERE A MISTAKE
and now I'm running into a completely different issue where the emulation stops, and the emulator looks like it's stopped on a breakpoint, but it apparently never tells the GDB remote about this. So it hangs forever
I could switch away from this janky untested hack version of the GDB protocol, except then I'd need a binary GDB compiled to match my target architecture, and I'm not sure one even exists.

@foone It's a network protocol, right?

Lowercasing proxy?