United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6474240 Check unhandled oops is too slow and hard to debug in jvmg
JDK-6474240 : Check unhandled oops is too slow and hard to debug in jvmg

Details
Type:
Bug
Submit Date:
2006-09-22
Status:
Closed
Updated Date:
2012-10-08
Project Name:
JDK
Resolved Date:
2006-11-14
Component:
hotspot
OS:
solaris
Sub-Component:
runtime
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs10 (b03)

Related Reports
Backport:
Backport:

Sub Tasks

Description
Title says it all.  CHECK_UNHANDLED_OOPS code is slow in jvmg because the studio compilers don't inline away the constructor destructor calls for oop so it's much slower than fastdebug just running without the option.  Also, if you're building a jvmg (debug) version of the VM, you usually want to debug the oops and they're hard to debug with a level of indirection.  Having this functionality is good for testing a fastdebug VM with but not jvmg, so it's only going to be enabled for fastdebug vm.

                                    

Comments
EVALUATION

Fixed 6474240: Check unhandled oops is too slow and hard to debug in jvmg

Took CHECK_UNHANDLED_OOPS out of jvmg.make and hopefully soon to be deprecated
debug.make.
                                     
2006-10-10



Hardware and Software, Engineered to Work Together