• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

src/25-Apr-2025-5,2103,395

.cargo-checksum.jsonD25-Apr-20253.3 KiB11

Android.bpD25-Apr-20251.3 KiB5449

CHANGELOG.mdD25-Apr-20251.4 KiB4727

Cargo.tomlD25-Apr-20251.2 KiB4339

LICENSED25-Apr-2025236 74

METADATAD25-Apr-2025424 1817

MODULE_LICENSE_MITD25-Apr-20250

README.mdD25-Apr-20251.1 KiB2418

TEST_MAPPINGD25-Apr-2025337 1918

cargo_embargo.jsonD25-Apr-202542 54

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