FULL PRODUCT VERSION :
java version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b110)
Java HotSpot(TM) Client VM (build 19.0-b06, mixed mode, sharing)

FULL OS VERSION :
Microsoft Windows [Version 5.2.3790]

A DESCRIPTION OF THE PROBLEM :
If HotSpotDiagnostics.dumpHeap() is called for application running on Java 7 b110, "Visual Studio Just-InTime Debugger" window shows up with message "An unhandled win32 exception occured".

This is a regression: the operation worked just fine with b107 and older (I did not check with b108-b109).

THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try

THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run any Java application and trigger heap dump.

Approach 1:

- Run any app, e.g. "java -jar SwingSet2.jar"
- Learn the PID via "jps"
- Invoke "jmap -dump:file=a.hprof,format=b <PID>"

Approach 2:

- Run jconsole
- Connect to itself
- MBeans -> com.sun.management -> HotSpotDiagnostic -> Operations -> press dumpHeap

ERROR MESSAGES/STACK TRACES THAT OCCUR :
hs_err_<pid>.log is not created

REPRODUCIBILITY :
This bug can be reproduced always.

Release Regression From : 7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.