-
Bug
-
Resolution: Fixed
-
P3
-
5.0
-
b50
-
generic
-
generic
-
Verified
There were two bugs filed for {-client, class share} mode core file attach failures. Those are
5030024 [solaris] and 5033011 [linux]
and were fixed by reading class share heap pages from classes[_g].jsa file. The fixes were verified in product mode.
But, the same failure (UnmappedAddressException is thrown) occurs with fastdebug mode. The fastdebug mode libjvm.so uses classes_g.jsa whereas SA uses classes.jsa whenever it sees libjvm.so in debuggee.
Refer to NSK SA/JDI attach test cases:
nsk/sajdi/SACoreAttachingConnector/attach/attach002
nsk/sajdi/SACoreAttachingConnector/attach/attach001
and core file attaching debug server connector test cases:
nsk/sajdi/SADebugServerAttachingConnector/attach/attach011
nsk/sajdi/SADebugServerAttachingConnector/attach/attach012
The above tests fail in {solaris, x86}, {linux, x86} and {solaris, sparc} platforms running with {-client, class share} mode.
###@###.### 2004-04-23
5030024 [solaris] and 5033011 [linux]
and were fixed by reading class share heap pages from classes[_g].jsa file. The fixes were verified in product mode.
But, the same failure (UnmappedAddressException is thrown) occurs with fastdebug mode. The fastdebug mode libjvm.so uses classes_g.jsa whereas SA uses classes.jsa whenever it sees libjvm.so in debuggee.
Refer to NSK SA/JDI attach test cases:
nsk/sajdi/SACoreAttachingConnector/attach/attach002
nsk/sajdi/SACoreAttachingConnector/attach/attach001
and core file attaching debug server connector test cases:
nsk/sajdi/SADebugServerAttachingConnector/attach/attach011
nsk/sajdi/SADebugServerAttachingConnector/attach/attach012
The above tests fail in {solaris, x86}, {linux, x86} and {solaris, sparc} platforms running with {-client, class share} mode.
###@###.### 2004-04-23
- relates to
-
JDK-5030024 SA utilities: UnmappedAddressException is thrown for core dumps with class shari
- Resolved
-
JDK-5033011 SA utilities: jstack throws UnmappedAddressException on Linux core dumps when cl
- Resolved