You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/06/22 15:15:30 UTC

[jira] Closed: (HARMONY-2693) [drlvm][jvmti] Incorrect direction flag value leads stack corruption

     [ https://issues.apache.org/jira/browse/HARMONY-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky closed HARMONY-2693.
--------------------------------------


No response, assuming ok.

> [drlvm][jvmti] Incorrect direction flag value leads stack corruption
> --------------------------------------------------------------------
>
>                 Key: HARMONY-2693
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2693
>             Project: Harmony
>          Issue Type: Bug
>         Environment: ia32, msvc 2003, debug
>            Reporter: Pavel Rebriy
>            Assignee: Gregory Shimansky
>         Attachments: incorrect-direction-flag-fix.patch, incorrect-direction-flag-fix.patch
>
>
> Windows vectored exception handler is executed with the same processor flags as in code where exception has occurred. As Microsoft compiler generates unsafe function prolog in debug mode, incorrect direction flag value may lead to undesirable results such as stack values corruption. 
> The problem is similar to H-2010, when vectored handler changes IP address and returns control to the OS the remaining part of handler can be executed with incorrect direction flag. So the assembler wrappers are required to reset/restore a direction flag.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.