commit | 76d4089f40c66532c946913835614cd2ae2bf788 | [log] [tgz] |
---|---|---|
author | Jorge E. Moreira <jemoreira@google.com> | Tue Nov 02 23:37:18 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Nov 02 23:37:18 2021 +0000 |
tree | 0959818890f8444cfbb63eaeba27010823f045ab | |
parent | f245376a628298b16c8f53027f1b3a25d0c7d3b3 [diff] | |
parent | 8410424afd86e43cc2d9ef00c5b0a76312a45444 [diff] |
[automerger skipped] DO NOT MERGE ANYWHERE Temporarily delete build files to avoid build break am: 8410424afd -s ours am skip reason: subject contains skip directive Original change: https://googleplex-android-review.googlesource.com/c/platform/external/rust/crates/gdbstub_arch/+/16176127 Change-Id: Id6cd339835c6a939c0069f8058ed95f418b71459
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!