Demo Data from EDBT 2026 / reviewers in the wild / expert
Baldip Bijlani
dblp:426/2698
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Program verification · 87% Program analysis · 13% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program verification › security property verification
memory safety verification |
0.9 | 1 | 2025 | Memory-Safety Verification of Open Programs with Angelic Assumptions · Proc. ACM Program. Lang. 2025 |
Program analysis
false positive detection |
0.3 | 1 | 2025 | Memory-Safety Verification of Open Programs with Angelic Assumptions · Proc. ACM Program. Lang. 2025 |
Methods — techniques the papers use, named apart from their topics
property-directed reasoning · 0.9pattern mining · 0.9large language model · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Memory-Safety Verification of Open Programs with Angelic AssumptionsabstractAn open program is one for which the complete source code is not available, which is a reality for real-world program verification. Software verification tools tend to assume the worst about any unconstrained behavior and this can yield an enormous number of spurious warnings for open programs. For any serious verification effort, the engineer must invest time up-front in building a suitable model (or mock) of any missing code, which is time-consuming and error-prone. Inaccuracies in the mocks can lead to incorrect verification results. In this paper, we demonstrate a technique that is capable of distinguishing between false positives and actual bugs from potential memory-safety violations in an open program with high accuracy. Central to the technique is the ability of making angelic assumptions about missing code. To accomplish this, we first mine a set of idiomatic patterns in buffer-manipulating programs using a large language model (LLM). This is complemented by a formal synthesis strategy that performs property-directed reasoning to select, adapt and instantiate these idiomatic patterns into angelic assumptions on the target program. Overall, our system, Seeker, guarantees that a program is deemed correct only if it can be verified under a well-defined set of “trusted” idiomatic patterns. In our experiments over a set of benchmarks curated from popular open-source software, our tool Seeker is able to identify 79% of the false positives with zero false negatives. Gourav Takhar, Baldip Bijlani, Prantik Chatterjee, Akash Lal, Subhajit Roy 0001 |
Proc. ACM Program. Lang. | 2 |