Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Tracking] forc debugger command #2350

Open
4 of 5 tasks
mitchmindtree opened this issue Jul 20, 2022 · 0 comments
Open
4 of 5 tasks

[Tracking] forc debugger command #2350

mitchmindtree opened this issue Jul 20, 2022 · 0 comments
Assignees
@sdankel
Labels
enhancement New feature or request forc forc-debug Everything related to forc-debug

Comments

@mitchmindtree
Copy link
Contributor

mitchmindtree commented Jul 20, 2022 •
edited by sdankel
Loading

Overview

The fuel-debugger is a CLI tool that acts as a FVM client and provides runtime debugging support for FVM bytecode.

We should provide a forc debugger (or forc dbg?) plugin that wraps and extends fuel-debugger with sway/forc-specific functionality.

This might include:

  • Configuration via forc manifest.
  • Debug build profile awareness.
  • Automatically sources contracts, bytecode from out/.
  • Ensures target is build before running the debugger (or alternatively, recommends running forc build if out/ artifacts don't exist yet).

FuelLabs/fuel-debugger#15 (comment)

TODO
@mitchmindtree mitchmindtree added enhancement New feature or request forc labels Jul 20, 2022
@mitchmindtree mitchmindtree mentioned this issue Jul 20, 2022
Closed
@sdankel sdankel self-assigned this Dec 13, 2023
@sdankel sdankel added forc-debug Everything related to forc-debug and removed debugger labels Dec 14, 2023
@sdankel sdankel mentioned this issue Dec 19, 2023
Merged
7 tasks
sdankel added a commit that referenced this issue Dec 20, 2023
@sdankel @JoshuaBatty
Refactor forc-test to expose VM interpreter (#5409)
d3da28d 
## Description

Related #2350

This refactor is not intended to change any behavior. It adds
`TestExecutor` which has a handle to `vm::Interpreter`. This will be
used to access the debugger within the VM.

Also moved the "setup" related code into a new file to make the code
more organized.

## Checklist

- [ ] I have linked to any relevant issues.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [ ] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [ ] I have requested a review from the relevant team or maintainers.

---------

Co-authored-by: Joshua Batty <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdankel sdankel

Labels
enhancement New feature or request forc forc-debug Everything related to forc-debug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitchmindtree @sdankel