You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Elena Semukhina (JIRA)" <ji...@apache.org> on 2007/01/16 12:12:28 UTC
[jira] Created: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
[drlvm][thread manager] 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
Attachments: MyStack.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.
-
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
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469754 ]
Alexey Varlamov commented on HARMONY-3010:
------------------------------------------
Reproduced on truly x86 SUSE10 SMP box, MyStack2 outputs on release build:
SIGSEGV in VM code.
Stack trace:
and hangs.
On Xeon SUSE9 32bit SMP box, it segfaults too but does not hangs and does not provide backtrace.
> [drlvm][thread manager] 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
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread] VM crashes with
seg fault on the recursive call of a synchronized method
Posted by "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.
[jira] Updated: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Elena Semukhina (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elena Semukhina updated HARMONY-3010:
-------------------------------------
Attachment: MyStack2.java
Pavel,
it's my fault: I erroneously attached the test which passed. Now I attach MyStack2.java which fails. The tests differ with "synchronized" modifier of the test() method.
Please try MyStack2.
> [drlvm][thread manager] 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
> 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.
[jira] Assigned: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn reassigned HARMONY-3010:
----------------------------------------
Assignee: weldon washburn
> [drlvm][thread manager] 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
> Assigned To: weldon washburn
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Elena Semukhina (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468607 ]
Elena Semukhina commented on HARMONY-3010:
------------------------------------------
Pavel,
my last suggestion is to limit stack size with ulimit -s 8192 if it is unlimited on your machine :). Although the test crashes for me even with unlimited stack size. If this does not help you to see the crash, I'll investigate this more thouroughly to see where I'm possibly wrong.
> [drlvm][thread manager] 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
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468572 ]
Pavel Afremov commented on HARMONY-3010:
----------------------------------------
I can't reproduce it now. The output on my machine is:
$ ./build/lnx_ia32_gcc_release/deploy/jdk/jre/bin/java -showversion -cp .. MyStack
Apache Harmony Launcher : (c) Copyright 1991, 2006 The Apache Software Foundation or its licensors, as applicable.
java version "1.5.0"
pre-alpha : not complete or compatible
svn = r@svn.revision@, (Jan 26 2007), Linux/ia32/gcc 3.3.3, release build
http://incubator.apache.org/harmony
Got expected StackOverflowError
Stack test passed
$ cat /etc/SuSE-release
SUSE LINUX Enterprise Server 9 (i586)
VERSION = 9
$
> [drlvm][thread manager] 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
> Attachments: MyStack.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.
[jira] Closed: (HARMONY-3010) [drlvm][thread] VM crashes with seg
fault on the recursive call of a synchronized method
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-3010.
--------------------------------------
Resolution: Cannot Reproduce
Assignee: Gregory Shimansky (was: weldon washburn)
Closed as not reproducible.
> [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: Gregory Shimansky
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468600 ]
Pavel Afremov commented on HARMONY-3010:
----------------------------------------
I ran test in the while true loop. Sorry, but result is the same:
$ ./build/lnx_ia32_gcc_release/deploy/jdk/jre/bin/java -showversion -cp .. MyStack2
Apache Harmony Launcher : (c) Copyright 1991, 2006 The Apache Software Foundation or its licensors, as applicable.
java version "1.5.0"
pre-alpha : not complete or compatible
svn = r@svn.revision@, (Jan 30 2007), Linux/ia32/gcc 3.3.3, release build
http://incubator.apache.org/harmony
Got expected StackOverflowError
Stack test passed
Now I try debug build.
> [drlvm][thread manager] 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
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468601 ]
Pavel Afremov commented on HARMONY-3010:
----------------------------------------
Debug version works perfect too:
$ ./build/lnx_ia32_gcc_release/deploy/jdk/jre/bin/java -showversion -cp .. MyStack2
Apache Harmony Launcher : (c) Copyright 1991, 2006 The Apache Software Foundation or its licensors, as applicable.
java version "1.5.0"
pre-alpha : not complete or compatible
svn = r@svn.revision@, (Jan 30 2007), Linux/ia32/gcc 3.3.3, release build
http://incubator.apache.org/harmony
Got expected StackOverflowError
Stack test passed
> [drlvm][thread manager] 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
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Peter Novodvorsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478768 ]
Peter Novodvorsky commented on HARMONY-3010:
--------------------------------------------
The problem is not in thread manager code. With the help of Pavel Afremov I've found that stack overflow happens, but it cannot be thrown while execution happens in code called from asm-helper (which is the case with thread_thin_monitor_try_enter). It tries to find previous M2N frame but it appears to be M2N frame above our thread starter which doesn't allow to throw exceptions from.
The reason why the fault happens in thread_thin_monitor_try_enter is because it's the most often called piece of code in the program.
Magics support in compiler could fix this problem.
> [drlvm][thread manager] 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
> Assigned To: weldon washburn
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485933 ]
weldon washburn commented on HARMONY-3010:
------------------------------------------
Its good to know the problem is not inside the Thread Manager code. One question. Will [vm]magics JIT support fix the entire problem? Standard vmmagics intrinsics only offers address arithmetic functions. Is there a need to push/pop the hardware stack? (I can't think how there could be a stack overflow without push/pop or something that reads/writes esp.)
> [drlvm][thread manager] 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
> Assigned To: weldon washburn
> 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.
[jira] Updated: (HARMONY-3010) [drlvm][thread] VM crashes with seg
fault on the recursive call of a synchronized method
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn updated HARMONY-3010:
-------------------------------------
Priority: Minor (was: Major)
> [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.
[jira] Updated: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Elena Semukhina (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elena Semukhina updated HARMONY-3010:
-------------------------------------
Attachment: MyStack.java
> [drlvm][thread manager] 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
> Attachments: MyStack.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.
-
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
[jira] Updated: (HARMONY-3010) [drlvm][thread] VM crashes with seg
fault on the recursive call of a synchronized method
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky updated HARMONY-3010:
---------------------------------------
Summary: [drlvm][thread] VM crashes with seg fault on the recursive call of a synchronized method (was: [drlvm][thread manager] VM crashes with seg fault on the recursive call of a synchronized method)
> [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
> Assigned To: weldon washburn
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread manager] VM crashes
with seg fault on the recursive call of a synchronized method
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468604 ]
Pavel Afremov commented on HARMONY-3010:
----------------------------------------
So for me, MyStack and MyStack2 woks without any problem. The crash stack trace looks very strange, sigsegv happen in hyThread library. It looks like bug in threading system. I saw something like it on x86_64 sometime ago, and by this reason I didn't contribute SOE support for x86_64 Linux platform..
> [drlvm][thread manager] 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
> 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.
[jira] Commented: (HARMONY-3010) [drlvm][thread] VM crashes with
seg fault on the recursive call of a synchronized method
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519580 ]
Mikhail Fursov commented on HARMONY-3010:
-----------------------------------------
This issue must be fixed after HARMONY-4292 is committed
> [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.