0.4.5

New Protocol Extensions

• TargetDescriptionXmlOverride - Allow targets to override the target description XML file (target.xml) specified by Target::Arch::target_description_xml. This is useful in cases where a Target is expected to be generic over multiple architectures. #43 (with help from DrChat)

0.4.4

Bugfixes

• use write! instead of writeln! in output! macro #41

0.4.3

New Arch Implementations

• Implement RegId for Mips/Mips64 #38 (starfleetcadet75)
• Implement RegId for MSP430 #38 (starfleetcadet75)

0.4.2

Packaging

• Exclude test object files from package #37 (keiichiw)

0.4.1

New Arch Implementations

• Implement RegId for x86/x86_64 #34 (keiichiw)

Bugfixes

• Switch fatal error signal from T06 to S05,
• specify cfg-if 0.1.10 or later #33 (keiichiw)
  • cargo build fails if cfg-if is 0.1.9 or older

Misc

• Don't hard-code u64 when parsing packets (use big-endian byte arrays + late conversion to Target::Arch::Usize).

0.4.0

This version includes a major API overhaul, alongside a slew of new features and general improvements. While updating to 0.4.0 will require some substantial code modifications, it's well worth the effort, as 0.4.0 is the safest, leanest, and most featureful release of gdbstub yet!

Fun fact: Even after adding a bunch of new features and bug-fixes, the in-tree example_no_std has remained just as small! The example on the semver-fix-0.2.2 branch is 20251 bytes, while the example on 0.4.0 is 20246 bytes.

API Changes

• Rewrite the Target API in terms of "Inlineable Dyn Extension Traits" (IDETs)
  • By breaking up Target into smaller pieces which can be mixed-and-matched, it not only makes it easier to get up-and-running with gdbstub, but it also unlocks a lot of awesome internal optimizations:
    • Substantially reduces binary-size footprint by guaranteeing dead-code-elimination of parsing/handling unimplemented GDB protocol features.
    • Compile-time enforcement that certain groups of methods are implemented in-tandem (e.g: add_sw_breakpoint and remove_sw_breakpoint).
• Update the Target API with support for non-fatal error handling.
  • The old approach of only allowing *fatal* errors was woefully inadequate when dealing with potentially fallible operations such as reading from unauthorized memory (which GDB likes to do a bunch), or handling non-fatal std::io::Error that occur as a result of ExtendedMode operations. The new TargetResult/TargetError result is much more robust, and opens to door to supporting additional error handling extensions (such as LLDB's ASCII Errors).
• Update the Connection trait with new methods (flush - required, write_all, on_session_start)
• Lift Registers::RegId to Arch::RegId, and introduce new temporary RegIdImpl solution for avoiding breaking API changes due to new RegId implementations (see #29)
• Mark various RegId enums as #[non_exhaustive], allowing more registers to be added if need be.
• Error types are now marked as #[non_exhaustive].

New Protocol Extensions

• ExtendedMode - Allow targets to run new processes / attach to existing processes / restart execution.
  • Includes support for set disable-randomization, set environment, set startup-with-shell, and set cwd and cd.
• SectionOffsets - Get section/segment relocation offsets from the target. #30 (mchesser)
  • Uses the qOffsets packet under-the-hood.

Bugfixes

• Fix issues related to selecting the incorrect thread after hitting a breakpoint in multi-threaded targets.
• Ensure that set_nodelay is set when using a TcpStream as a Connection (via the new Connection::on_session_start API)
  • This should result in a noticeable performance improvement when debugging over TCP.

Misc

• Removed btou dependency.
• Removed all UTF-8 aware str handling code.
  • GDB uses a pure ASCII protocol, so including code to deal with UTF-8 resulted in unnecessary binary bloat.

0.3.0

This is a semver-compatible re-release of 0.2.2.

0.2.2 - yanked

This version contains a few minor breaking changes from 0.2.1. These are only surface-level changes, and can be fixed with minimal effort.

Version 0.3.0 is identical to the yanked version 0.2.2, except that it adheres to cargo's modified SemVer rule which states that the pre-0.x.y breaking changes should still bump the minor version.

Thanks to h33p for reporting this issue (#27)

• Add Target::read/write_register support (to support single register accesses) #22 (thomashk0)
• Update Target::resume API to replace raw &mut dyn Iterator with a functionally identical concrete Actions iterator.
• Mark the StopReason enum as non-exhaustive, allowing further types to be added without being considered "breaking changes"
• Add StopReason::Signal(u8) variant, to send arbitrary signal codes #19 (mchesser)
• New arch implementations:
  • Add partial RISC-V support (only integer ISA at the moment) #21 (thomashk0)
  • Add i386 (x86) support #23 (jamcleod)
  • Add 32-bit PowerPC support #25 (jamcleod)

0.2.1

• Add x86_86 support #11 (jamcleod)
• Add Mips and Mips64 support #13 (starfleetcadet75)
• Documentation improvements
  • Document PC adjustment requirements in Target::resume
  • Add docs on handling non-fatal invalid memory reads/writes in Target::read/write_addrs.