[ http://issues.apache.org/jira/browse/HARMONY-1427?page=comments#action_12435335 ]
weldon washburn commented on HARMONY-1427:
------------------------------------------
Rewriting in JNI probably explains the change in suspend mode state. GC suspend needs to
be enabled before entering a JNI function. It turns out that the JNI mechanism will toggle
suspend enable/disable at the appropriate times internally.
> [drlvm] ExceptionDescribe incorrectly disables suspend when calling exn_print_stack_trace
> -----------------------------------------------------------------------------------------
>
> Key: HARMONY-1427
> URL: http://issues.apache.org/jira/browse/HARMONY-1427
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Gregory Shimansky
> Attachments: JNI-ExceptionDescribe.patch
>
>
> Looks like the mode in which exn_print_stack_trace works has changed. It is now suspend_enabled,
and inside of this function there is an assertion that suspend is enabled. But the change
was not applied to JNI ExceptionDescribe function. It still disables suspend when calling
exn_print_stack_trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|