New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toggle support for QStartNoAckMode
#135
Conversation
Good start, but you'll also need to tweak the code in Some pointers on that:
And doing so will have knock-on effects in The end result is that |
gdbstub/src/protocol/commands.rs Lines 249 to 251 in bf4ad90
It seems that this code is used when the packet received is parsed? But |
Yes, to be clear: I'm saying that you should move the |
Even if we don't include |
If the The details of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, this LGTM! (docs outstanding)
I'll merge this in later today, and cut a new release with this feature included.
Thanks again for the contribution!
@@ -530,6 +530,14 @@ pub trait Target { | |||
<Self::Arch as Arch>::single_step_gdb_behavior() | |||
} | |||
|
|||
/// Enable/disable `QStartNoAckMode` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think these docs are up to snuff...
That said, for expediency's sake, I don't mind cleaning these up after merge.
In the future though, docs should avoid mentioning the nitty-gritty details of their underlying implementation whenever possible, and instead, be written from the perspective of user-visible behavior. The point of gdbstub
is that users really shouldn't care what a QStartNoAckMode
packet is.
i.e: i'll tweak these docs to paraphrase from https://sourceware.org/gdb/onlinedocs/gdb/Packet-Acknowledgment.html#Packet-Acknowledgment
gdbstub 0.6.6 has been published to crates.io |
Description
This PR makes the feature
QStartNoAckMode
toggleable.Closes #134
API Stability
Checklist
rustdoc
formatting looks good (viacargo doc
)examples/armv4t
withRUST_LOG=trace
+ any relevant GDB output under the "Validation" section below./example_no_std/check_size.sh
before/after changes under the "Validation" section belowexamples/armv4t
./example_no_std/check_size.sh
)Arch
implementationValidation
Before/After `./example_no_std/check_size.sh` output
Before
After 2bc3d4f
After 3e7e6a8