-
Enhancement
-
Resolution: Fixed
-
P1
-
1.4.2_05
-
b63
-
sparc
-
solaris_9
When a Java app is compiled with "javac -g", information that correlates byte codes back to source lines is inserted in the class files.
When the Hotspot run-time compiler compiles some of those byte codes, that source line correlation is lost. The source-line info is needed by Sun's Collect/Analyzer tools to correlate performance information with specific lines or blocks of code. The performance information includes time spent, cache misses, TLB misses, etc. For C, C++, and Fortran, the Collect/Analyzer is incredibly useful at showing the developer what part of the code is taking the most time. For Java, Collect/Analyzer can't provide the same degree of detail. For code that is compiled at run-time, Collect/Analyzer can report only by method, not by source line.
Please preserve this line number information when code is compiled at run-time.
###@###.### 10/7/04 15:23 GMT
When the Hotspot run-time compiler compiles some of those byte codes, that source line correlation is lost. The source-line info is needed by Sun's Collect/Analyzer tools to correlate performance information with specific lines or blocks of code. The performance information includes time spent, cache misses, TLB misses, etc. For C, C++, and Fortran, the Collect/Analyzer is incredibly useful at showing the developer what part of the code is taking the most time. For Java, Collect/Analyzer can't provide the same degree of detail. For code that is compiled at run-time, Collect/Analyzer can report only by method, not by source line.
Please preserve this line number information when code is compiled at run-time.
###@###.### 10/7/04 15:23 GMT
- relates to
-
JDK-6359840 Forte collector plugin misuses debug-info accessor to query backtrace
-
- Resolved
-
-
JDK-6379830 JVM crash when running sun studio 11 performance analyzer
-
- Resolved
-