commit | 5fb9c425adfd43e9aff125904e9efa11d1b9dd52 | [log] [tgz] |
---|---|---|
author | Jeff Vander Stoep <jeffv@google.com> | Tue Jan 31 21:50:16 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jan 31 21:50:16 2023 +0000 |
tree | e24db05b09991006ebdd1f63ed2451d768640aab | |
parent | 7933fd1768c7f2b11126b308daa01d4858508771 [diff] | |
parent | 3ae41e070cee37026af79b0e6035d5e106e14cd1 [diff] |
Update TEST_MAPPING am: ab1c426703 am: 64ca3415cf am: 3ae41e070c Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/gdbstub_arch/+/2411480 Change-Id: I902a79c5e100530aa6865c46ac7822b79272bb55 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!