Demo Data from EDBT 2026 / reviewers in the wild / expert
Mark H. Weaver
dblp:23/6938
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1994
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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 |
Debugging and program repair · 50% Operating systems · 50% |
Topics — the 1 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Operating systems › fault tolerance
checkpoint and rollback |
0.0 | 1 | 1994 | Optimal Tracing and Incremental Reexecution for Debugging Long-Running Programs · PLDI 1994 |
Methods — techniques the papers use, named apart from their topics
two-level bitvectors · 0.0adaptive tracing · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1994 | Optimal Tracing and Incremental Reexecution for Debugging Long-Running ProgramsabstractDebugging requires execution replay. Locations of bugs are rarely known in advance, so an execution must be repeated over and over to track down bugs. A problem arises with repeated reexecution for long-running programs and programs that have complex interactions with their environment. Replaying long-running programs from the start incurs too much delay. Replaying programs that interact with their environment requires the difficult (and sometimes impossible) task of exactly reproducing this environment (such as the connections over a one-day period to an X server). We solve these problems by incremental checkpointing and replay. By periodically checkpointing parts of the execution''s state, it can be restarted from intermediate points, bounding the delay to replay any part of the execution and allowing parts of the execution to be skipped. We present adaptive tracing strategies that provide bounded-time incremental replay and that are nearly optimal. Our techniques track reads and writes to memory using space-efficient two-level bitvectors. Our implementation on a Sparc 10 traces less than 15 kilobytes/sec for CPU-intensive programs and for interactive programs the slowdown is low enough that tracing can be left on all the time. Robert H. B. Netzer, Mark H. Weaver |
PLDI | 2 |