1992
DOI: 10.1007/978-1-4471-3501-2_15
|View full text |Cite
|
Sign up to set email alerts
|

Systems for Late Code Modification

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

1993
1993
2008
2008

Publication Types

Select...
6
3
1

Relationship

0
10

Authors

Journals

citations
Cited by 39 publications
(10 citation statements)
references
References 9 publications
0
10
0
Order By: Relevance
“…Each program and operating system was instrumented with epoxie [10, 37], which is a program that rewrites assembly code to record a complete address trace Assertion Implication 1. The operating system has less instruction and data locality…”
Section: Trace Overviewmentioning
confidence: 99%
“…Each program and operating system was instrumented with epoxie [10, 37], which is a program that rewrites assembly code to record a complete address trace Assertion Implication 1. The operating system has less instruction and data locality…”
Section: Trace Overviewmentioning
confidence: 99%
“…An alternative approach is to instrument the application code prior to execution, for example, during compilation [17], at the assembly language or object code [18] levels, at link time [19], or by rewriting the final executable [20,21]. Using controlflow analysis the quantity of information generated at trace capture time can be reduced substantially.…”
Section: Code Annotationmentioning
confidence: 99%
“…For memory references we have to solve the aliasing problem [26,12]: decide whether two memory references access the same location. We have to prove that two references always point to the same location (must-alias) or must show that they never refer to the same location.…”
Section: Introductionmentioning
confidence: 99%