Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P1
Fix Version/s: hs17
Affects Version/s: 6u16
Component/s: hotspot
Labels:
- regression
- stopper

Subcomponent:
runtime
Introduced In Version:

6u10
Resolved In Build:
b09
CPU:

x86
OS:

windows

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2188209	7	Daniel Daugherty	P1	Closed	Fixed	b83
JDK-2189838	6u21	Daniel Daugherty	P1	Closed	Fixed	b01
JDK-2188407	6u19	Daniel Daugherty	P1	Closed	Fixed	b03
JDK-2189071	OpenJDK6	Daniel Daugherty	P1	Closed	Fixed	b19
JDK-2188373	hs16.2	Daniel Daugherty	P1	Closed	Fixed	b03

On Windows, when a process calls SetUnhandledExceptionFilter to register its own filter F, then calls JNI_CreateJavaVM to attach a 1.6.0_16 JVM, and then (in native code, in a thread not attached to the VM) writes through a null pointer, the filter F is not called. It used to be called, in the exact same scenario, at least with the 1.5.0_06 JVM, so this appears to be a regression.

backported by

JDK-2188209 in-process JVM now ignores preset Windows unhandled exception filter

Closed

JDK-2188373 in-process JVM now ignores preset Windows unhandled exception filter

Closed

JDK-2188407 in-process JVM now ignores preset Windows unhandled exception filter

Closed

JDK-2189071 in-process JVM now ignores preset Windows unhandled exception filter

Closed

JDK-2189838 in-process JVM now ignores preset Windows unhandled exception filter

Closed

relates to

JDK-6550813 Crash because of FPU control word being modified by native code (win32)

Closed

(1 relates to)

Assignee:: Daniel Daugherty
Reporter:: J. Duke
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: 2010-01-20 08:42
Updated:: 2012-10-08 00:51
Resolved:: 2010-02-09 12:31
Imported:: 17/Sep/12 7:31 AM
Indexed:: 19/Jul/12 10:38 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates