Poor man's watchpoints

Authors:
Max Copperman;Jeff Thomas
Affiliations:
Xerox Palo Alto Research Center, 3333 Coyote Hill Road, Palo Alto, CA;Kubota Pacific Computer, Inc., 2630 Walsh Avenue, Santa Clara, CA
Venue:
ACM SIGPLAN Notices
Year:
1995

Citing 4
Cited 4

Fast breakpoints: design and implementation

PLDI '90 Proceedings of the ACM SIGPLAN 1990 conference on Programming language design and implementation
Efficient data breakpoints

ASPLOS V Proceedings of the fifth international conference on Architectural support for programming languages and operating systems
Practical data breakpoints: design and implementation

PLDI '93 Proceedings of the ACM SIGPLAN 1993 conference on Programming language design and implementation
Rewriting executable files to measure program behavior

Software—Practice & Experience

Dynamic currency determination in optimized programs

ACM Transactions on Programming Languages and Systems (TOPLAS)
A compact execution history for dynamic slicing

Information Processing Letters
DynaTest and beyond: From dynamic testing to automated error-prevention and error-detection

Journal of Computational Methods in Sciences and Engineering - Selected papers from the International Conference on Computer Science,Software Engineering, Information Technology, e-Business, and Applications, 2003
How to do a million watchpoints: efficient debugging using dynamic instrumentation

CC'08/ETAPS'08 Proceedings of the Joint European Conferences on Theory and Practice of Software 17th international conference on Compiler construction

Quantified Score

Hi-index	0.00

Visualization

Abstract

Bugs that result from corruption of program data can be very difficult to track down without specialized help from a debugger. If the debugger cannot help the user find the point at which data gets corrupted, the user may have a long iterative debugging task. If the debugger is able to stop execution of the program at the point where data gets corrupted, as with watchpoints (also known as data breakpoints), it may be a very simple task to find a data corruption bug. In this paper, we discuss a method of implementing watchpoints on a system without hardware watchpoint support. By instrumenting the program code to check memory accesses, and supplying an interface to the instrumentation in the debugger, we provide an efficient, general method of implementing watchpoints.