Daniel Prilik

> Also - I noticed that there is a new `pc()` function on the `Registers` trait. _sigh_ this is another vestigial bit of infrastructure left over from when I took...

Which bit specifically? Dynamic `Arch` selection as a whole is a larger design problem, one which I've already had a couple of false-starts on fixing in the past. Fixing this...

Thanks for popping open the issue - always good to know what protocol features folks are interested in! A cursory glance through the protocol docs suggests that this should be...

> A TLS extension might be useful for single threaded targets as well, because single threads could still have TLS, could they not? Yes? But also, I'm not sure if...

Ahh, this is a fair point. In that case, we should also include an implementation for single threaded targets as well. We'd probably want to take a similar approach to...

Thank you for bringing this critical omission to light. Based on some cursory research (you'll have to apologize - I'm clearly an uncultured programmer who lacks experience working with such...

Thank you for the contribution! This is certainly one of the more interesting Arch implementations I've seen, and I'm looking forward to merging it in :) * * * wrt....

> Okay, let me suggest a fourth one, then! I read through your suggestion, and yeah, I think that'd work! Quite elegantly at that, I might add! There is one...

> In this context (which might not hold for other architectures) [...] Ahh, yeah, unfortunately, this doesn't hold for other architectures. The contents of the `g`/`G` packet isn't related to...

> But I don't see a way to control that at run-time or even in the `Target` implementation: if the architecture mandates supporting FP, how can we tell beforehand if...