Crates.io | firedbg-cli |
lib.rs | firedbg-cli |
version | 1.74.0 |
source | src |
created_at | 2023-12-11 08:14:18.992881 |
updated_at | 2023-12-11 08:14:18.992881 |
description | FireDBG command line interface |
homepage | https://firedbg.sea-ql.org |
repository | https://github.com/SeaQL/FireDBG.for.Rust |
max_upload_size | |
id | 1064837 |
size | 97,915 |
firedbg-cli
is a CLI to invoke all FireDBG operations.
The firedbg
command can only act on Cargo Workspace. If you have a simple dependency free rust file, you still need to put it under a cargo workspace for firedbg
to work properly.
There are two ways to tell firedbg
where is the root directory of a cargo workspace:
--workspace-root
option, i.e. firedbg --workspace-root <WORKSPACE-ROOT>
cache
: Parse all .rs
source files in the current workspaceclean
: Cleanup the firedbg/
folderlist-target
: List all runnable targetsrun
: Run a binary target with debugging enabledexample
: Run an example with debugging enabledtest
: Run an integrated test with debugging enabledunit-test
: Run a unit test with debugging enabledindex
: Run indexer on the latest run and save it as a .sqlite
db filelist-run
: List all firedbg
runsopen
: Open debugger view in VS Codehelp
: Print help message or the help of the given subcommand(s)You can get the help messages by appending the --help
flag.
firedbg.toml
Config FileBy default FireDBG will only trace the function calls of the debugging package. If you want to trace other packages in your local workspace, you will need to create a firedbg.toml
config file on your workspace root.
[workspace.members]
quicksort = { trace = "full" }
# Syntax: <PACKAGE> = { trace = "<full | none>" }