paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Checking LTL[F,G,X] on compressed traces in polynomial time

在压缩轨迹上以多项式时间检查 LTL[F,G,X]
FSE Proceedings of the 29th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering2021匹配度 3/10 · 该论文属于形式化验证/LTL 运行时验证,与程序验证和压缩轨迹分析相关;但用户核心方向聚焦于 LLM/Agent 与静态分析/形式化验证的交叉、浮点程序分析及贝叶斯程序分析,本文未涉及这些关键交叉点,也未体现工业落地或 benchmark 失效分析。引用 1 inbox
Minjian Zhang, Umang Mathur, Mahesh Viswanathan
crossref: 2026-09-12

AI 速览

一句话:提出直接检查压缩执行轨迹上 LTL[F,G,X] 性质的多项式时间算法,避免先解压。

程序执行是否满足形式规范是运行时验证与测试预言等任务中的核心问题。当无法在线分析时,执行轨迹日志常被压缩存储,以便离线事后分析并降低磁盘与仓储开销。直接方法通常是先解压再检查,但会带来额外成本。本文研究如何在不解压的前提下,直接对压缩轨迹检查带 F、G、X 算子的 LTL 规范,并给出多项式时间算法。其目标是在压缩表示上保持 LTL 验证的可判定性与高效性,从而支持可扩展的离线运行时验证与测试预言。摘要未展开具体压缩模型与实现细节。

问题
在离线运行时验证与测试预言场景中,如何避免先解压执行轨迹,直接判断压缩轨迹是否满足 LTL[F,G,X] 规范。
方法
针对压缩轨迹表示设计直接检查算法,而非先解压后分析;标题表明其核心是在压缩轨迹上以多项式时间完成 LTL[F,G,X] 检查。
评估
摘要未给出实验评估,主要评估维度是算法复杂度保证;标题明确强调 polynomial time。
原文摘要(Abstract)

The problem of checking if a program execution meets a formal specification arises in many software engineering tasks including runtime verification and designing test oracles. When online analysis is not possible, execution trace logs are stored for offline postmortem analysis, often in a compressed format to reduce disk space and warehousing requirements. A straightforward method for checking if a compressed execution satisfies a property is to first decompress it and then analyze the resulting uncompressed execution.

链接与引用

DOI 原文 ·

BibTeX
@inproceedings{paperbot6385,
  title = {Checking LTL[F,G,X] on compressed traces in polynomial time},
  author = {Minjian Zhang and Umang Mathur and Mahesh Viswanathan},
  booktitle = {FSE},
  year = {2021},
  doi = {10.1145/3468264.3468557}
}