commit | 7a68f95bda294a1421834695ba67b8843badc293 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Thu Nov 09 03:11:02 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 09 03:11:02 2023 +0000 |
tree | 923159a36e459235b9ccfeeb6542f5482d2e424e | |
parent | bd3219cbfb35a73479ba3603bc4be0970d3e80a5 [diff] | |
parent | c2131991dab065497524b97c1767956512eb1710 [diff] |
Migrate to cargo_embargo. am: efbeffa602 am: c2131991da Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/gdbstub_arch/+/2823090 Change-Id: I3b2c2ae3f3e660b58c53f5992a8564451d02a148 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Community-contributed implementations of gdbstub::arch::Arch
for various architectures.
Note: If an architecture is missing from this crate, that does not mean that it can't be used with gdbstub
! So-long as there's support for the target architecture in GDB, it should be fairly straightforward to implement Arch
manually.
Please consider upstreaming any missing Arch
implementations you happen to implement yourself! Aside from the altruistic motive of improving gdbstub
, upstreaming your Arch
implementation will ensure that it's kept up-to-date with any future breaking API changes.
Disclaimer: These implementations are all community contributions, and while they are tested (by the PR's author) and code-reviewed, it's not particularly feasible to write detailed tests for each architecture! If you spot a bug in any of the implementations, please file an issue / open a PR!