You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Pervov (JIRA)" <ji...@apache.org> on 2006/11/27 10:53:21 UTC
[jira] Created: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
[drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
--------------------------------------------------------------------------------------------
Key: HARMONY-2327
URL: http://issues.apache.org/jira/browse/HARMONY-2327
Project: Harmony
Issue Type: Bug
Components: DRLVM
Reporter: Pavel Pervov
There are call paths where contradictory suspension states are required.
For example:
void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
assert(!hythread_is_suspend_enabled());
exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
assert(hythread_is_suspend_enabled());
Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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
[jira] Updated: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2327?page=all ]
Pavel Afremov updated HARMONY-2327:
-----------------------------------
Attachment: Fix-of-enumeration-safety-state-inconsistence-on-exceptions-call-stacks.txt
Fix of enumeration safety state inconsistence on exceptions call stacks.
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: http://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assigned To: Gregory Shimansky
> Attachments: Fix-of-enumeration-safety-state-inconsistence-on-exceptions-call-stacks.txt
>
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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
[jira] Commented: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Pavel Pervov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2327?page=comments#action_12453590 ]
Pavel Pervov commented on HARMONY-2327:
---------------------------------------
I'll prepare the patch for this.
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: http://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assigned To: Gregory Shimansky
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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
[jira] Updated: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2327?page=all ]
Gregory Shimansky updated HARMONY-2327:
---------------------------------------
Patch Info: [Patch Available]
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: http://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assigned To: Gregory Shimansky
> Attachments: Fix-of-enumeration-safety-state-inconsistence-on-exceptions-call-stacks.txt
>
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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
[jira] Resolved: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2327?page=all ]
Gregory Shimansky resolved HARMONY-2327.
----------------------------------------
Resolution: Fixed
Patch applied at 481113. Please check that it was applied as expected.
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: http://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assigned To: Gregory Shimansky
> Attachments: Fix-of-enumeration-safety-state-inconsistence-on-exceptions-call-stacks.txt
>
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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
[jira] Closed: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-2327.
--------------------------------------
No response, assuming ok.
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: https://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assignee: Gregory Shimansky
> Attachments: Fix-of-enumeration-safety-state-inconsistence-on-exceptions-call-stacks.txt
>
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-2327) [drlvm][exceptions] enumeration
safety state is inconsistent through exceptions call stacks.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2327?page=all ]
Gregory Shimansky reassigned HARMONY-2327:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][exceptions] enumeration safety state is inconsistent through exceptions call stacks.
> --------------------------------------------------------------------------------------------
>
> Key: HARMONY-2327
> URL: http://issues.apache.org/jira/browse/HARMONY-2327
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Pavel Pervov
> Assigned To: Gregory Shimansky
>
> There are call paths where contradictory suspension states are required.
> For example:
> void exn_throw_by_name(const char* exc_name, const char* exc_message, jthrowable exc_cause)
> assert(!hythread_is_suspend_enabled());
> exn_throw_by_name_internal(exc_name, exc_message, exc_cause);
> assert(hythread_is_suspend_enabled());
> Such paths fail and lead to assertions in debug VM, when exceptions are thrown from within VM code.
--
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