ACM Home Page
Please provide us with feedback. Feedback
Recompilation for debugging support in a JIT-compiler
Full text PdfPdf (90 KB)
Source Workshop on Program Analysis for Software Tools and Engineering archive
Proceedings of the 2002 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering table of contents
Charleston, South Carolina, USA
SESSION: Monitoring and debugging table of contents
Pages: 10 - 17  
Year of Publication: 2002
ISBN:1-58113-479-7
Also published in ...
Authors
Mustafa M. Tikir  University of Maryland, College Park, MD
Jeffrey K. Hollingsworth  University of Maryland, College Park, MD
Guei-Yuan Lueh  Intel Corporation, Santa Clara, CA
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 20,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/586094.586100
What is a DOI?

ABSTRACT

A static Java compiler converts Java source code into a verifiably secure and compact architecture-neutral intermediate format, called Java byte codes. The Java byte codes can be either interpreted by a Java Virtual Machine or translated into native code by Java Just-In-Time compilers. Static Java compilers embed debug information in the Java class files to be used by the source level debuggers. However, the debug information is generated for architecture independent byte codes and most of the debug information is valid only when the byte codes are interpreted. Translating byte codes into native instructions puts a limitation on the amount of usable debug information that can be used by source level debuggers. In this paper, we present a new technique to generate valid debug information when Just-In-Time compilers are used. Our approach is based on the dynamic recompilation of Java methods by a fast code generator and lazily generates debug information when it is required. We also present three implementations for field watch support in the Java Virtual Machine Debugger Interface to investigate the runtime overhead and code size growth by our approach.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
Sun Microsystems, Java Virtual Machine Debug Interface Reference. http://java.sun.com/j2se/1.3/docs/guide/jpda/jvmdi-spec.html
 
4
 
5
 
6
 
7
Intel Corp. Intel Architecture Software Developer's Manual, 1997 (Order number 243192).
 
8
Intel Corp. Intel IA-64 Architecture Software Developer's Manual, 2000 (Order number 245319).
 
9
10
 
11
Standard Performance Evaluation Corporation. SPEC JVM98 Benchmarks, http://www.spec.org/osg/jvm98
 
12
13
 
14
Intel Corporation, Open Runtime Platform. http://www.intel.com/research/mrl/orp.
15
16
 
17
18

Collaborative Colleagues:
Mustafa M. Tikir: colleagues
Jeffrey K. Hollingsworth: colleagues
Guei-Yuan Lueh: colleagues