An API for Runtime Code Patching

By B. Buck, Jeffrey K. Hollingsworth. The international journal of high performance computing applications, 2000

647 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

An infrastructure for adaptive dynamic optimization (2003, background): “Dyninst is based on dynamic instrumen- tation technology [20] developed as part of the Paradyn Par- allel Performance Tools project [29].”
The Tau Parallel Performance System (2006, methodology): “Our approach for TAU uses the DyninstAPI to construct calls to the TAU measurement library and then insert these calls into the executable code.”
Pin: building customized program analysis tools with dynamic instrumentation (2005, methodology): “Example probe-ba s d systems include Dyninst [7], Vulcan [29], and DTrace [9].”
HPCTOOLKIT: tools for performance analysis of optimized parallel programs (2010, methodology): “Other tools analyze unmodified application binaries by using dynamic instrumentation [3, 7, 14, 22] or library preloading [6, 9, 16, 25, 29].”
Dynamic software updating (2001, methodology): “At the other extreme of the .exibility axis are systems that, like ours, allow nearly arbitrary changes to programs at runtime [Lee 1983; Frieder and Segal 1991; Gupta et al. 1996; Armstrong et al. 1996; Bloom 1983].”