harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Popov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3314) [drlvm][shutdown][thread] DRLVM hangs on exit while detaching thread
Date Fri, 18 May 2007 15:29:16 GMT

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

Ivan Popov commented on HARMONY-3314:
-------------------------------------

Weldon,

I've checked this problem with the fresh Harmony build (r539299) and I could not see VM hangs
for JPDA tests, even running JPDA test in a long loop. However, after I ran EUT test suite
for jdtdebug component, I still see a couple of hung VM processes. Attaching to them with
MSVC debugger I see lot of GC threads and one VM thread executing some Java method. Unfortunately,
I could not print java stack  trace, but it seems similar a picture described in my comment
above [20/Mar/07 08:35 AM]. It seems the initial threading problem was not resolved, but now
it occurs very rarely, so this problem is not critical now.

According to the stack trace in the last comment, it is a different issue, related to JPDA
implementation. It seems the problem is in EventDispatcher code which is executed in threads
#3 and #4. However, this situation looks strange to me. When thread #4 reaches this point
it has already sent notify message to thread #3 and set stop flag, so thread #3 should wake
up, check stop flag, and finish. However, thread #3 is still in waiting. There is already
suggestion in HARMONY-3269 to make VM shutdown less sensitive to JPDA synchronization problems,
it may prevent such situations.

I'll try to reproduce both failures and look deeply what happened there, but again this issue
is not critical now.



> [drlvm][shutdown][thread] DRLVM hangs on exit while detaching thread
> --------------------------------------------------------------------
>
>                 Key: HARMONY-3314
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3314
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM, JDK
>         Environment: Linux/ia32, Windows/ia32, Harmony-jdk-r514598, Harmony-jdk-r533073
>            Reporter: Ivan Popov
>         Assigned To: weldon washburn
>
> Many JDWP tests run long time on Linux because DRLVM intermittently crashed at exit.
> For example, the following test
>   org.apache.harmony.jpda.tests.jdwp.Events.VMDeathTest
> Here is typical diagnostics in the test output:
> Waiting for debuggee exit
> STDERR> SIGSEGV in VM code.
> STDERR> Stack trace:
> STDERR> 	1: ?? (??:-1)
> STDERR> addr2line: '[heap]': No such file
> Ignoring exception in ProcessWaiter thread interrupted: java.lang.InterruptedException
> # ERROR: Enforced debuggee termination
> To reproduce this failure:
> 1. create Harmony JDK with federated build:
>     svn checkout https://svn.apache.org/repos/asf/harmony/enhanced/trunk
>     cd trunk
>     ant
> 2. goto jdktools directory, add junit to classpath, and run particular test:
>     cd working_jdktools
>     export CLASSPATH=<...>/trunk/common_resources/depends/jars/junit_3.8.2/junit.jar
>     ant test -Dbuild.module=jpda -Dtest.case=org.apache.harmony.jpda.tests.jdwp.Events.VMDeathTest
> 3. see results in <...>/trunk/working_jdktools/build/test_report/html/index.html
> It is possible also to run test directly from command line:
>    cd working_jdktools
>    deploy/jdk/bin/java -classpath ../common_resources/depends/jars/junit_3.8.2/junit.jar:build/tests/classes
\
>    org.apache.harmony.jpda.tests.jdwp.Events.VMDeathTest

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


Mime
View raw message