Google Git
Sign in
android / platform / external / rust / crates / gdbstub_arch / refs/tags/aml_tet_331711040
tagb667eb5f8e4f3bf8f9896d38fdca4cf119b7b9e8
taggerThe Android Open Source Project <initial-contribution@android.com>Fri May 26 06:22:18 2023 -0700
objectf7a97fbc0c1eb721f39af3354c422bb114bb2b31 
aml_tet_331711040
commitf7a97fbc0c1eb721f39af3354c422bb114bb2b31[log] [tgz]
authorJoel Galenson <jgalenson@google.com>Wed Dec 15 18:07:26 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Dec 15 18:07:26 2021 +0000
treefcb1a58c331cc338a961249db2b8726b6c5f69ff
parentb62826d1f46ddf4a95ed728feb2a7ee964ac5045 [diff]
parentb7797056e63640fac47141258f49f41417dde570 [diff]
Merge "Refresh Android.bp, cargo2android.json, TEST_MAPPING." am: 554e9d1da7 am: 245b7615f2 am: a696195954 am: b7797056e6

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/gdbstub_arch/+/1912498

Change-Id: I801071c5bed9ffb5014a26ae419d0c48a0b57478
tree: fcb1a58c331cc338a961249db2b8726b6c5f69ff
  1. src/
  2. .cargo_vcs_info.json
  3. Android.bp
  4. Cargo.toml
  5. Cargo.toml.orig
  6. cargo2android.json
  7. LICENSE
  8. METADATA
  9. MODULE_LICENSE_MIT
  10. OWNERS
  11. README.md
  12. TEST_MAPPING
README.md

gdbstub_arch

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!