Backend
Keeping Fuzzers on Duty: Repairing Fuzzing Build Breakages in Continuous Open-Source Fuzzing
arXiv cs.SE0 views
arXiv:2611.06358v1 Announce Type: new Abstract: Continuous fuzzing platforms such as OSS-Fuzz provide sustained security testing for open-source projects, but long-term build breakages reduce security coverage and waste infrastructure resources. In OSS-Fuzz, around 20% of integrated projects remain in build-failure states, leaving their fuzzers off duty. These failures expose a maintenance gap between platform maintainers, who lack project-specific context, and project maintainers, who often lack fuzzing and infrastructure expertise. Existing program-repair techniques cannot be directly applied because fuzz build breakages span evolving project and infrastructure artifacts and require repeated infrastructure-aware diagnosis. We present FuzzMedic, an automated agent for fuzz build repair. FuzzMedic performs evidence-guided diagnosis across project and fuzzing-infrastructure artifacts. It explores repairs over a repair-state graph (RSG) that records the evolving workspace and build feedback. Branching and rollback enable FuzzMedic to recover from unproductive repair paths during long-horizon debugging. Candidate patches are validated to restore executable fuzz targets rather than merely suppress build failures. We evaluate FuzzMedic on 128 reproducible OSS-Fuzz build failures extracted from 1,820 real-world failures. FuzzMedic achieves a 48.44% repair rate and outperforms three representative program-repair baselines. In real-world use, it produces 29 patches merged into upstream or OSS-Fuzz main branches, including repairs for three failures that had remained unresolved for more than one year and two cases that had never built successfully.
Source:https://arxiv.org/abs/2611.06358PreviousEvoCodeAgent: Project-Level Code Generation via Architecture-Code Co-Evolution and Experience-Guided RepairNextReassessing Dataset Quality and Fine-Tuning Practices for Vulnerability Detection on PrimeVul dataset
Related posts
How to let Claude Code and Codex talk directly across two computers without copy-pasting logs
0dev.to
Why Is There a Delay When I’m Typing? (I Tested the Bottlenecks So You Don’t Have To)
0dev.to

Moving City GIS Into Unreal Engine: Coordinate Systems, LOD, and the Boring Parts
0dev.to
My AI Agent Said 'Done.' It Wasn't. A Field Guide to Trusting Nothing an Agent Tells You
0dev.to
Bridging Context and Execution: An Engineering Assessment of Connected AI Workflows
0dev.to
把 AI CLI 包成 OpenAI 相容 API:從 stdin、JSON 輸出到逾時處理(附可跑範例)
0dev.to