7.1 KiB
Changelog
All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
0.4.5
New Protocol Extensions
TargetDescriptionXmlOverride
- Allow targets to override the target description XML file (target.xml
) specified byTarget::Arch::target_description_xml
. This is useful in cases where aTarget
is expected to be generic over multiple architectures. #43 (with help from DrChat)
0.4.4
Bugfixes
- use
write!
instead ofwriteln!
inoutput!
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
0.4.1
New Arch Implementations
Bugfixes
- Switch fatal error signal from
T06
toS05
, - 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 withgdbstub
, 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
andremove_sw_breakpoint
).
- By breaking up
- 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 ofExtendedMode
operations. The newTargetResult
/TargetError
result is much more robust, and opens to door to supporting additional error handling extensions (such as LLDB's ASCII Errors).
- 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
- Update the
Connection
trait with new methods (flush
- required,write_all
,on_session_start
) - Lift
Registers::RegId
toArch::RegId
, and introduce new temporaryRegIdImpl
solution for avoiding breaking API changes due to newRegId
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
, andset cwd
andcd
.
- Includes support for
SectionOffsets
- Get section/segment relocation offsets from the target. #30 (mchesser)- Uses the
qOffsets
packet under-the-hood.
- Uses the
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 aTcpStream
as aConnection
(via the newConnection::on_session_start
API)- This should result in a noticeable performance improvement when debugging over TCP.
Misc
- Removed
btou
dependency. - Removed all
UTF-8
awarestr
handling code.- GDB uses a pure ASCII protocol, so including code to deal with UTF-8 resulted in unnecessary binary bloat.
0.3.0 (formerly 0.2.2)
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)
API Changes
- Update
Target::resume
API to replace raw&mut dyn Iterator
with a functionally identical concreteActions
iterator. - Mark the
StopReason
enum as#[non_exhaustive]
, allowing further types to be added without being considered as an API breaking change.
New Protocol Extensions
- Add
Target::read/write_register
support (to support single register accesses) #22 (thomashk0) - 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
New Arch Implementations
- Add x86_86 support #11 (jamcleod)
- Add Mips and Mips64 support #13 (starfleetcadet75)
Misc
- Documentation improvements
- Document PC adjustment requirements in
Target::resume
- Add docs on handling non-fatal invalid memory reads/writes in
Target::read/write_addrs
.
- Document PC adjustment requirements in
0.2.0
start of changelog