Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Memory Analyzer (MAT) » jextract error => DTLJ failure?
jextract error => DTLJ failure? [message #7675] Sat, 22 November 2008 18:40 Go to previous message
Paul E. Keyser is currently offline Paul E. Keyser
Messages: 878
Registered: July 2009
Senior Member
WInXP; IBM JVM:

java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pwi32dev-20070511 (SR5))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
j9vmwi3223-20070426 (JIT enabled)
J9VM - 20070420_12448_lHdSMR
JIT - 20070419_1806_r8
GC - 200704_19)
JCL - 20070511

Rather often when running "jextract" (from that JVM) to create the zip
necessary for DTLJ, jextract reports (these are all the cases):

could not read J9Class (464 bytes) at 059B5E68

could not read J9Class (480 bytes) at 05C03E68

could not read J9Class (456 bytes) at 063EAE60

could not read J9Class (464 bytes) at 05BC6E90

could not read J9Class (456 bytes) at 05687E88

could not read J9Class (464 bytes) at 05CEAE90

What's up with that?

I also often have the result that MAT+DTLJ reports no memory usage by
anyone except the class-loaders; if that bogus report occurs, it has
always (so far) been the case that one of the above errors in jextract
had occurred. (But some of the jextract errors did not seem to lead to
DTLJ errors.)

any ideas?

thanks,
Paul
 
Read Message
Read Message
Read Message
Previous Topic:Gray part in Overview pane
Next Topic:error in instructions: no way to get HPROF from Sun JVM 1.5
Goto Forum:
  


Current Time: Sat May 25 22:21:48 EDT 2013

Powered by FUDForum. Page generated in 0.01658 seconds