-
Notifications
You must be signed in to change notification settings - Fork 848
Add Firewood state dump tooling for targeted block-height debugging #5226
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.
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -285,7 +285,7 @@ if [[ -n "${CHAOS_MODE:-}" ]]; then | |
| --max-wait-time="${MAX_WAIT_TIME}" \ | ||
| --config="${CONFIG}" | ||
| else | ||
| go run github.com/ava-labs/avalanchego/tests/reexecute/c \ | ||
| go run ./tests/reexecute/c \ | ||
| --block-dir="${BLOCK_DIR}" \ | ||
|
Comment on lines
287
to
289
|
||
| --current-state-dir="${CURRENT_STATE_DIR}" \ | ||
| ${RUNNER_TYPE:+--runner="${RUNNER_TYPE}"} \ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DumpProposalcallsp.handle.Dump()(Firewood FFI) while holdingt.proposalsmutex. IfDump()is slow, this blocks commits/proposals/updates that also need the same lock, undermining the stated goal of not blocking proposal operations during dumps. Consider selecting the handle + any metadata under the lock, releasing the lock, then performing the FFI dump; if concurrent commit/drop is a concern, add a dedicated handle-level lock/refcount soDump()andCommit()/Drop()can’t race.