Skip to content

OSS-Fuzz: Add new fuzzer/corpus/dict targets tree exec - #1277

Merged
facontidavide merged 4 commits into
BehaviorTree:masterfrom
arthurscchan:behaviortreecpp-tree-exec
Nov 7, 2026
Merged

facontidavide merged 4 commits into
BehaviorTree:masterfrom
arthurscchan:behaviortreecpp-tree-exec

Conversation

@arthurscchan

Copy link
Copy Markdown
Contributor

This PR adds a new OSS-Fuzz fuzzerwith corpus/dict targets tree exec, together with google/oss-fuzz#16434 to enable a new fuzzer for project behaviortreecpp.

arthurscchan and others added 4 commits November 3, 2026 08:20
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
Remove the "btcpp-1" / findings/ / coverage-pipeline references and the
unused wakeup_aware variable, and flatten the nested anonymous namespace.
No change in what the fuzzer generates or consumes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@facontidavide

Copy link
Copy Markdown
Collaborator

Thanks @arthurscchan, this is the most useful of the three: until now nothing in OSS-Fuzz ticked a tree.

I pushed one commit (ee9832f) on top of a merge of master. It removes the references to files that aren't in this repository (findings/bt_tree_exec_fuzzer/README.md, "btcpp-1", the coverage-pipeline report) and the unused wakeup_aware variable, and flattens the nested anonymous namespace. The generated trees and the consumed bytes are unchanged. It builds with clang-21 and ran clean for 60 s on the seed corpus (about 915 exec/s).

The ~Tree() abort you worked around is real, and I reproduced it on master: #1281. Once that's fixed we can generate catch_on_halt="true" again. I'll squash-merge this once CI is green.

Heads-up: #1277, #1278 and #1279 all edit the same line of cmake/fuzzing_build.cmake, so the other two will need a rebase.

@facontidavide
facontidavide merged commit 12bfc0a into BehaviorTree:master Nov 7, 2026
17 checks passed
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.

2 participants