Daniel Prilik

> > Though fwiw, I would just inline the `.len()` implementation, which would invalidate both of those last two bullet points :) > > Is that possible for a `pub`...

PR is merged, and `gdbstub 0.6.3` + `gdbstub_arch 0.2.4` are both published 🎉

Hey @luser, thanks for the heads up! Glad to know that when the time comes, `gdbstub` can ~crib your code with impunity~ reuse some of your excellent work :wink: Yeah,...

@Sladuca Go for it! Any and all contributions are always welcome. If you ever need any guidance on how to structure the feature and/or how to tackle certain problems, feel...

I have spent quite a bit of time toying around with this, and ended up hacking together an implementation that _works_, but misses the mark in terms of API ergonomics....

@DrChat thanks for the feedback, I really appreciate it! Glad to hear that `gdbstub` is working as expected. * * * Funny enough, the API you're proposing is actually what...

To preface, here is a brief overview of the current `read/write_registers` implementation: ``` (alloc A) GDB Packet (ASCII, hex encoded, Big Endian) (in GDB-specific order) Size: N (alloc A) GDB...

> but `RegId::from_raw_id()` also returns a register size parameter, which can vary depending on the target architecture Ah, this is a very fair point, since the register size parameter determines...

Heck, I don't even provide a proper example of how to work with the current `Actions` based API in-tree (the `armv4t_multicore` example is _pretty bad_), so I'm not surprised it's...

Thanks for reaching out @xobs! I'm really glad you did, since validating `gdbstub`'s bare-metal use case is something I've been meaning to do for a [_very_ long time](https://github.com/daniel5151/gdbstub/commit/7daf21bc5930ca882596ca4736183e69d2b3f490#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R159). I have...