-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P1
-
Affects Version/s: 1.1.5
-
Component/s: client-libs
-
None
-
1.1.5
-
sparc
-
solaris_2.6
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2017159 | 1.2.0 | Mike Bronson | P1 | Resolved | Fixed | 1.2 |
In awt_MToolkit.c, function awt_MToolkit_loop did *not* check whether
the call to XtAppPeekEvent returned True or False. A True return value
indicates that it found an X event on the queue, a False value that it
did not. But if it returned False, this code went ahead and switched on
the event type in xev.type anyway, which may contain garbage on the stack.
In that case, the execution of this switch was unsafe and unpredictable.
the call to XtAppPeekEvent returned True or False. A True return value
indicates that it found an X event on the queue, a False value that it
did not. But if it returned False, this code went ahead and switched on
the event type in xev.type anyway, which may contain garbage on the stack.
In that case, the execution of this switch was unsafe and unpredictable.
- backported by
-
JDK-2017159 awt_MToolkit_loop switches on xev.type, which may contain garbage.
-
- Resolved
-
- relates to
-
-
- Closed
-