Skip to content

tests/fuzz/fuzz-open_channel: fix bad local variable access after longjmp#9165

Open
whitslack wants to merge 1 commit into
ElementsProject:masterfrom
whitslack:fix-fuzz-open_channel
Open

tests/fuzz/fuzz-open_channel: fix bad local variable access after longjmp#9165
whitslack wants to merge 1 commit into
ElementsProject:masterfrom
whitslack:fix-fuzz-open_channel

Conversation

@whitslack
Copy link
Copy Markdown
Collaborator

You can't access a local variable from a point before it was initialized and expect it to have the initialized value. Move the setjmp() call to after run_ctx is initialized so that the tal_free() call at cleanup will see the correct address and not crash.

Fixes: #9131

Checklist

Before submitting the PR, ensure the following tasks are completed. If an item is not applicable to your PR, please mark it as checked:

  • The changelog has been updated in the relevant commit(s) according to the guidelines.
  • Tests have been added or modified to reflect the changes. N/A
  • Documentation has been reviewed and updated as needed. N/A
  • Related issues have been listed and linked, including any that this PR closes.
  • Important All PRs must consider how to reverse any persistent changes for tools/lightning-downgrade N/A

…gjmp

You can't access a local variable from a point before it was initialized and
expect it to have the initialized value. Move the setjmp() call to after
run_ctx is initialized so that the tal_free() call at cleanup will see the
correct address and not crash.

Fixes: ElementsProject#9131
Changelog-None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v26.06rc1: fuzz-open_channel Error 134 (or "Aborted")

1 participant