You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "George Timoshenko (JIRA)" <ji...@apache.org> on 2007/01/12 09:52:27 UTC

[jira] Updated: (HARMONY-2981) [drlvm][jit][opt]SPECjbb2005 silently exit on EM64T (OPT mode)

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

George Timoshenko updated HARMONY-2981:
---------------------------------------

    Description: 
Release build exits right after printing:

Calling Reporter

Debug build now is falling with assertion. But last year (in december) when I started the investigations it was also failing at the same point with SIGSEGV somwhere in managed code.

Investigations shows that the problem was in Ia32StackInfo and Ia32StackLayout.
Wrong types of some variables led to incorrect value in 'rsp' register after context restoration before exception hadler entering.

The patch is coming soon.

  was:
Release build exits right after printing:

Calling Reporter

Debug build now if falling with assertion? but last year (in december) when I started the investigations it also failed at the same place with SIGSEGV somwhere in managed code.

Investigations shows that the problem was in Ia32StackInfo and Ia32StackLayout.
Wrong types of some variables led to incorrect value in 'rsp' register after context restoration before exception hadler entering.

The patch is coming soon.


> [drlvm][jit][opt]SPECjbb2005 silently exit on EM64T (OPT mode)
> --------------------------------------------------------------
>
>                 Key: HARMONY-2981
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2981
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: EM64T
>            Reporter: George Timoshenko
>
> Release build exits right after printing:
> Calling Reporter
> Debug build now is falling with assertion. But last year (in december) when I started the investigations it was also failing at the same point with SIGSEGV somwhere in managed code.
> Investigations shows that the problem was in Ia32StackInfo and Ia32StackLayout.
> Wrong types of some variables led to incorrect value in 'rsp' register after context restoration before exception hadler entering.
> The patch is coming soon.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira