Some demos generating Segmentation Fault using -d64 option with solaris-amd64 binaries

Some demos generating Segmentation Fault using -d64 option with solaris-amd64 binaries.

- This bug was introduced with Mustang B49. Initially assigning to classes_awt for evaluation as this is a problem with GUI applications. Could also be VM issues as both AWT and VM had putbacks with B49.

- Seen only with solaris-amd64 binaries with AMD64 Opteron running Solaris10 (reproducible on two different machines).

- The Segmentation Faults occur often but not everytime when running J2SE demos such as Font2DTest, Java2Demo, or SwingSet2. So far unable to reproduce with NotePad or StylePad demos.

- The Segmentation Faults will happen either at launch or after immediately clicking on the window close box after the application launches. Usually happens after only a few attempts.

- If the -d64 option is left out, the demos run properly so there is a workaround.

Steps to reproduce:
==================
1) Set JAVA_HOME to use solaris-amd64 binaries (Build 49 or later)
2) On AMD Opteron 64 machine, run a demo application (Font2DTest, Java2Demo, or SwingSet2):

$JAVA_HOME/bin/java -d64 -jar Font2DTest.jar

3) If the Segmentation Fault does not occur at launch, then click on the window close button after the application launches. May only take a few attempts to reproduce.

A "core" file will be generated. Very large to attach to this bug. A sample core file is available at:
/net/sqe1.sfbay.sun.com/quality2/swing/client-dtf/java/j2se160_binaries/solaris-amd64/demo/jfc/Font2DTest