[jira] Commented: (HARMONY-3010) [drlvm][thread] VM crashes with seg fault on the recursive call of a synchronized method

["Pavel Rebriy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553281 ] 

Pavel Rebriy commented on HARMONY-3010:
---------------------------------------

I've checked the tests on revision  603614 - both tests passed.
I think bug is already fixed and could be closed.

> [drlvm][thread] VM crashes with seg fault on the recursive call of a synchronized method
> ----------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3010
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3010
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Elena Semukhina
>            Assignee: weldon washburn
>            Priority: Minor
>         Attachments: MyStack.java, MyStack2.java
>
>
> The attached test crashes with the following message on Linux SUSE9 ia32:
> SIGSEGV in VM code.
> Stack trace:
>         1: locktable_get_fat_monitor (/nfs/ins/proj/drl/coreapi/esemukhi/svn/drlvm/trunk/vm/thread/src/thread_native_thin_monitor.c:655)
>         2: hythread_thin_monitor_try_enter (/nfs/ins/proj/drl/coreapi/esemukhi/svn/drlvm/trunk/vm/thread/src/thread_native_thin_monitor.c:310)
>         3: IP is 0x416A05BD <native code>
>         4: ?? (??:-1)
> <end of stack trace>
> Segmentation fault
> If to remove the "synchronized" modifier from the "test()" method declaration, the test passes.
> On SUSE9 Linux em64t the crash does not depend on the "synchronized" modifier: it just crashes with the wording:
> Segmentation fault
> (see HARMONY-2972)
> The attached test is the slightly modified smoke test stress.Stack.

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