跳到正文
研踪PaperTrail

论文库

检索计算机领域论文,按研究方向、作者或关键词筛选。

部分采集异常
正在读取账号与研究记录…

全站更新概况

+979新增论文
+781其中 AI 相关
+119已有论文修订
+95新增 AI 导读

arXiv 最近完成扫描:2026-11-20 08:48 · 全站最近入库:2026-11-20 19:58各信源进度 →

统计口径与数据新鲜度

统计 2026-11-20 02:13 — 2026-11-21 02:13(北京时间) · 点击数字查看对应简报;AI 相关包含在新增论文内。

最近完成检查:2026-11-20 08:48最近发现新增版本:2026-11-20 19:58库内论文最新更新时间:2026-11-20 02:59

每分钟刷新已保存的数据。空检查不代表采集异常;新收录可能包含历史论文。AI 导读按新增版本计数。

28,961 已收录论文24,030 AI 相关8,912 有修订112 HF 社区发现

浏览论文库

时间范围跟随排序:版本更新、本站收录或首次发表。最新收录可能包含历史论文。部分信源异常,查看状态 →

找到 1 篇论文 · 按版本更新时间排序上轮扫描起点 2026-11-20 08:46(北京时间)
新论文 · v1arXiv:2611.23336

RootSink: Reproducible C/C++ Crashes with Tested Repair Sites

Suryansh Singh Sijwali, Achintya Lakshmanan, Abhiram Dodda, Shaiful Chowdhury, Suman Saha

原文摘要

When a C or C++ program crashes on a crafted input, the line that crashes is often not the line that is wrong. Tools and models that repair or locate vulnerabilities need examples showing both, with evidence for each, which existing datasets rarely provide. RootSink provides 3341 records from 354 open-source projects. Most give the crash site a memory-error detector reported and a candidate location for its root cause, and label each with a weakness type and its evidence. For the 1954 records in the Reproduced tier, we re-ran the crash ourselves and confirmed that the fixed version runs cleanly. In 1275 of these, a single hunk of the developer's fix stopped the crash on its own. That marks a tested repair site, though not necessarily the defect, and 1273 records use it as the root. In a blind audit of an earlier version, two co-author raters called 68% and 92% of the tested repair sites they saw the defect, but only 37% and 51% of that version's located Reproduced-tier roots. RootSink ships with tasks, a patch scorer and run logs.

cs.SE