• Home
Name Date Size #Lines LOC

..--

src/03-May-2024-5,2883,442

.cargo_vcs_info.jsonD03-May-2024106 66

Android.bpD03-May-20241.4 KiB5954

CHANGELOG.mdD03-May-20241.3 KiB4124

Cargo.tomlD03-May-20241.2 KiB4339

Cargo.toml.origD03-May-2024689 1916

LICENSED03-May-2024236 74

METADATAD03-May-2024423 2019

MODULE_LICENSE_MITD03-May-20240

OWNERSD03-May-202447 21

README.mdD03-May-20241.1 KiB2418

TEST_MAPPINGD03-May-2024337 1918

cargo2android.jsonD03-May-202452 55

README.md

1# gdbstub_arch
2
3[![](https://img.shields.io/crates/v/gdbstub_arch.svg)](https://crates.io/crates/gdbstub_arch)
4[![](https://docs.rs/gdbstub_arch/badge.svg)](https://docs.rs/gdbstub_arch)
5[![](https://img.shields.io/badge/license-MIT%2FApache-blue.svg)](./LICENSE)
6
7Community-contributed implementations of `gdbstub::arch::Arch` for various
8architectures.
9
10_Note:_ If an architecture is missing from this crate, that does _not_ mean
11that it can't be used with `gdbstub`! So-long as there's support for the
12target architecture in GDB, it should be fairly straightforward to implement
13`Arch` manually.
14
15Please consider upstreaming any missing `Arch` implementations you happen to
16implement yourself! Aside from the altruistic motive of improving `gdbstub`,
17upstreaming your `Arch` implementation will ensure that it's kept up-to-date
18with any future breaking API changes.
19
20**Disclaimer:** These implementations are all community contributions, and
21while they are tested (by the PR's author) and code-reviewed, it's not
22particularly feasible to write detailed tests for each architecture! If you
23spot a bug in any of the implementations, please file an issue / open a PR!
24