Le-Chun Wu

dblp:46/1019 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1999
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

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 · 77% Compilers and program optimization · 23%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Debugging and program repair › software debugging
debugging optimized code
0.011999
A New Framework for Debugging Globally Optimized Code · PLDI 1999
Compilers and program optimization
optimizing compiler
0.011999
A New Framework for Debugging Globally Optimized Code · PLDI 1999

Methods — techniques the papers use, named apart from their topics

emulation-based forward recovery · 0.0
YearPublicationVenuePosition
1999 A New Framework for Debugging Globally Optimized Code
abstract
With an increasing number of executable binaries generated by optimizing compilers today, providing a clear and correct source-level debugger for programmers to debug optimized code has become a necessity. In this paper, a new framework for debugging globally optimized code is proposed. This framework consists of a new code location mapping scheme, a data location tracking scheme, and an emulation-based forward recovery model. By taking over the control early and emulating instructions selectively, the debugger can preserve and gather the required program state for the recovery of expected variable values at source breakpoints. The framework has been prototyped in the IMPACT compiler and GDB-4.16. Preliminary experiments conducted on several SPEC95 integer programs have yielded encouraging results. The extra time needed for the debugger to calculate the limits of the emulated region and to emulate instructions is hardly noticeable, while the increase in executable file size due to the extra debug information is on average 76% of that of the executable file with no debug information.
Le-Chun Wu, Rajiv Mirani, Harish Patil, Bruce Olsen, Wen-Mei W. Hwu
PLDI1