build(deps): bump gdbstub from 0.5.0 to 0.6.2

[dependabot]

Bumps gdbstub from 0.5.0 to 0.6.2.

Release notes

Sourced from gdbstub's releases.

0.6.2

New Protocol Extensions

• MultiThreadBase > ThreadExtraInfo - Provide extra information per-thread. #106 (thefaxman)
• LldbRegisterInfo - (LLDB specific) Report register information in the LLDB format. #103 (jawilk)
  • This information can be statically included as part of the Arch implemention, or dynamically reported via the LldbRegisterInfoOverride IDET.

Bugfixes

• Report thread ID in response to ? packet. #105 (thefaxman)

Internal Improvements

• Tweak enabled clippy lints
• Added a light dusting of #[inline] across the packet parsing code, crunching the code down even further
• Expanded on "no-panic guarantee" docs

0.6.1

• Add LLDB-specific HostIoOpenFlags #100 (mrk)

0.6.0

After over a half-year of development, gdbstub 0.6 has finally been released!

This massive release delivers a slew of new protocol extensions, internal improvements, and key API improvements. Some highlights include:

• A new non-blocking GdbStubStateMachine API, enabling gdbstub to integrate nicely with async event loops!
  • Moreover, on no_std platforms, this new API enables gdbstub to be driven directly via breakpoint/serial interrupt handlers!
  • This API is already being used in several Rust kernel projects, such as vmware-labs/node-replicated-kernel and betrusted-io/xous-core to enable bare-metal, in-kernel debugging.
• gdbstub is now entirely panic free in release builds!
  • * subject to rustc's compiler optimizations
  • This was a pretty painstaking effort, but the end result is a substantial reduction in binary size on no_std platforms.
• Tons of new and exciting protocol extensions, including but not limited to:
  • Support for remote file I/O (reading/writing files to the debug target)
  • Fetching remote memory maps
  • Catching + reporting syscall entry/exit conditions
  • ...and many more!
• A new license: gdbtsub is licensed under MIT OR Apache-2.0

See the changelog for a comprehensive rundown of all the new features.

While this release does come with quite a few breaking changes, the core IDET-based Target API has remained much the same, which should make porting code over from 0.5.x to 0.6 pretty mechanical. See the transition_guide.md for guidance on upgrading from 0.5.x to 0.6.

And as always, a huge shoutout to the folks who contributed PRs, Issues, and ideas to gdbstub - this release wouldn't have been possible without you! Special shoutouts to gz and xobs for helping me test and iterate on the new bare-metal state machine API, and bet4it for pointing out and implementing many useful API improvements and internal refactors.

Cheers!

New Features

• The new GdbStubStateMachine API gives users the power and flexibility to integrate gdbstub into their project-specific event loop infrastructure.

... (truncated)

Changelog

Sourced from gdbstub's changelog.

0.6.2

New Protocol Extensions

• MultiThreadBase > ThreadExtraInfo - Provide extra information per-thread. #106 (thefaxman)
• LldbRegisterInfo - (LLDB specific) Report register information in the LLDB format. #103 (jawilk)
  • This information can be statically included as part of the Arch implemention, or dynamically reported via the LldbRegisterInfoOverride IDET.

Bugfixes

• Report thread ID in response to ? packet. #105 (thefaxman)

Internal Improvements

• Tweak enabled clippy lints
• Added a light dusting of #[inline] across the packet parsing code, crunching the code down even further
• Expanded on "no-panic guarantee" docs

0.6.1

New Features

• add LLDB-specific HostIoOpenFlags #100 (mrk)

0.6.0

After over a half-year of development, gdbstub 0.6 has finally been released!

This massive release delivers a slew of new protocol extensions, internal improvements, and key API improvements. Some highlights include:

• A new non-blocking GdbStubStateMachine API, enabling gdbstub to integrate nicely with async event loops!
  • Moreover, on no_std platforms, this new API enables gdbstub to be driven directly via breakpoint/serial interrupt handlers!
  • This API is already being used in several Rust kernel projects, such as vmware-labs/node-replicated-kernel and betrusted-io/xous-core to enable bare-metal, in-kernel debugging.
• gdbstub is now entirely panic free in release builds!
  • * subject to rustc's compiler optimizations
  • This was a pretty painstaking effort, but the end result is a substantial reduction in binary size on no_std platforms.
• Tons of new and exciting protocol extensions, including but not limited to:
  • Support for remote file I/O (reading/writing files to the debug target)
  • Fetching remote memory maps
  • Catching + reporting syscall entry/exit conditions
  • ...and many more!
• A new license: gdbstub is licensed under MIT OR Apache-2.0

See the changelog for a comprehensive rundown of all the new features.

While this release does come with quite a few breaking changes, the core IDET-based Target API has remained much the same, which should make porting code over from 0.5.x to 0.6 pretty mechanical. See the transition_guide.md for guidance on upgrading from 0.5.x to 0.6.

And as always, a huge shoutout to the folks who contributed PRs, Issues, and ideas to gdbstub - this release wouldn't have been possible without you! Special shoutouts to gz and xobs for helping me test and iterate on the new bare-metal state machine API, and bet4it for pointing out and implementing many useful API improvements and internal refactors.

Cheers!

... (truncated)

Commits

• 51c8ba9 release gdbstub 0.6.2 and gdbstub_arch 0.2.3
• b584ae0 update PR template
• b862599 fix nightly rustfmt ci
• 5caa7b9 gdbstub_arch: fix missing reg_id in armv4t
• 4a8f325 s/register_info/lldb_register_info/g
• 9b6fd55 add qRegisterInfo packet support (#103)
• 6fce31a Add support for qThreadExtraInfo (#106)
• 2cd3bc6 Report thread-id in response to ? packet (#105)
• 1fde6f7 fix crosvm link
• a05db47 a light dusting of #[inline]
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #86.