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.

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

Fix bug in triaging stack func #657

Merged
merged 1 commit into from
Sep 30, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions experiment/builder_runner.py
Original file line number Diff line number Diff line change
Expand Up @@ -415,11 +415,10 @@ def _parse_libfuzzer_logs(self,
SemanticCheckResult(SemanticCheckResult.FP_NEAR_INIT_CRASH, symptom,
crash_stacks, crash_func))

# FP case 3: 1st func of the 1st thread stack is in fuzz target.
# FP case 3: no func in 1st thread stack belongs to testing proj.
if len(crash_stacks) > 0:
first_stack = crash_stacks[0]
# Check the first stack frame of the first stack only.
for stack_frame in first_stack[:1]:
for stack_frame in first_stack:
if self._stack_func_is_of_testing_project(stack_frame):
if 'LLVMFuzzerTestOneInput' in stack_frame:
return ParseResult(
Expand Down
Loading