You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Naveen Neelakantam (JIRA)" <ji...@apache.org> on 2006/12/19 19:50:21 UTC
[jira] Created: (HARMONY-2804) StackTest and gc.Mark fail if
vm.jitrino built in debug
StackTest and gc.Mark fail if vm.jitrino built in debug
-------------------------------------------------------
Key: HARMONY-2804
URL: http://issues.apache.org/jira/browse/HARMONY-2804
Project: Harmony
Issue Type: Bug
Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
Reporter: Naveen Neelakantam
Priority: Critical
I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2804?page=comments#action_12460071 ]
Naveen Neelakantam commented on HARMONY-2804:
---------------------------------------------
If I run StackTest manually I get the following output:
> java -cp . StackTest
java: /home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp:495: virtual void Jitrino::Ia32::RuntimeInterface::getGCRootSet(Jitrino::MethodDesc*, Jitrino::GCInterface*, const JitFrameContext*, bool): Assertion `0' failed.
SIGABRT in VM code.
Stack trace:
1: ?? (??:-1)
2: ?? (??:-1)
3: ?? (??:-1)
4: Jitrino::Ia32::RuntimeInterface::getGCRootSet(Jitrino::MethodDesc*, Jitrino::GCInterface*, JitFrameContext const*, bool) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp:495)
5: Jitrino::Jitrino::GetGCRootSet(Jitrino::MethodDesc*, Jitrino::GCInterface*, JitFrameContext const*, bool) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/main/Jitrino.cpp:304)
6: JIT_get_root_set_from_stack_frame (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/vm/drl/DrlJITInterface.cpp:374)
7: Dll_JIT::get_root_set_from_stack_frame(Method*, void*, JitFrameContext const*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/include/dll_jit_intf.h:104)
8: vm_enumerate_root_set_single_thread_on_stack(StackIterator*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/gc/root_set_enum_common.cpp:258)
9: vm_enumerate_thread(VM_thread*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/gc/stop_the_world_root_set_enum.cpp:225)
10: vm_enumerate_the_current_thread (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/gc/stop_the_world_root_set_enum.cpp:63)
11: stop_the_world_root_set_enumeration (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/gc/stop_the_world_root_set_enum.cpp:119)
12: vm_enumerate_root_set_all_threads (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/gc/stop_the_world_root_set_enum.cpp:150)
13: enumerate_universe (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/gc_cc/src/collect.cpp:138)
14: copy_gc(int) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/gc_cc/src/collect.cpp:375)
15: select_gc(int) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/gc_cc/src/selector.cpp:96)
16: gc_alloc (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/gc_cc/src/gc_for_vm.cpp:272)
17: NewLongArray(JNIEnv_External*, int) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jni/jni_array.cpp:433)
18: JNIEnv_External::NewLongArray(int) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/include/jni.h:1468)
19: Java_org_apache_harmony_vm_VMStack_getStackState (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/kernel_classes/native/org_apache_harmony_vm_VMStack.cpp:195)
20: IP is 0xA5934B2F <native code>
21: java/lang/Throwable.fillInStackTrace()Ljava/lang/Throwable; (??:-1)
22: java/lang/Throwable.<init>()V (??:-1)
23: java/lang/Error.<init>()V (Error.java:38)
24: java/lang/VirtualMachineError.<init>()V (VirtualMachineError.java:35)
25: java/lang/StackOverflowError.<init>()V (StackOverflowError.java:35)
26: vm_invoke_native_array_stub (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/ia32/base/invoke_native_stub_ia32.asm:41)
27: JIT_execute_method_default(void*, _jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/ia32/base/ini_iA32.cpp:199)
28: DrlEMImpl::executeMethod(_jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/DrlEMImpl.cpp:514)
29: ExecuteMethod (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/em_intf.cpp:43)
30: vm_execute_java_method_array(_jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jit/ini.cpp:51)
31: class_alloc_new_object_and_run_constructor(Class*, Method*, unsigned char*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jit/jit_runtime_support.cpp:2156)
32: create_lazy_exception (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/exception/exceptions_jit.cpp:151)
33: exn_propagate_exception (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/exception/exceptions_jit.cpp:304)
34: exn_athrow_regs(Registers*, Class*, bool) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/exception/exceptions_jit.cpp:468)
35: throw_from_sigcontext (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/linux/signals_ia32.cpp:155)
36: java_throw_from_sigcontext (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/linux/signals_ia32.cpp:174)
37: stack_overflow_handler(int, siginfo*, void*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/linux/signals_ia32.cpp:457)
38: null_java_reference_handler(int, siginfo*, void*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/linux/signals_ia32.cpp:484)
39: general_signal_handler(int, siginfo*, void*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/linux/signals_ia32.cpp:714)
40: ?? (??:-1)
<end of stack trace>
Abort
When I run gc.Mark manually I get this output (which looks similar to the error reported in HARMONY-2805):
allocating 400 Mb on 2 workers with 10 sleepers, live size 100 Mb, pause threshold 120 ms
SIGSEGV in VM code.
Stack trace:
1: Jitrino::Ia32::GCSafePoint::isHardwareExceptionPoint() const (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.h:102)
2: Jitrino::Ia32::hwecompare::operator()(Jitrino::Ia32::GCSafePoint const*, Jitrino::Ia32::GCSafePoint const*) const (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp:221)
3: ?? (00302d7d
:302)
4: ?? (00302751
:302751)
5: ?? (00301baa
:301)
6: ?? (003003f0
:3003)
7: Jitrino::Ia32::GCMap::write(unsigned char*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp:239)
8: Jitrino::Ia32::InfoBlockWriter::runImpl() (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp:528)
9: Jitrino::Ia32::SessionAction::run() (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/codegenerator/ia32/Ia32IRManager.cpp:2155)
10: Jitrino::runPipeline(Jitrino::CompilationContext*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/main/Jitrino.cpp:226)
11: Jitrino::compileMethod(Jitrino::CompilationContext*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/main/Jitrino.cpp:261)
12: Jitrino::Jitrino::CompileMethod(Jitrino::CompilationContext*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/main/Jitrino.cpp:286)
13: JIT_compile_method_with_params (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/jitrino/src/vm/drl/DrlJITInterface.cpp:278)
14: Dll_JIT::compile_method_with_params(void*, Method*, OpenMethodExecutionParams) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/include/dll_jit_intf.h:86)
15: compile_do_compilation_jit(Method*, JIT*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jit/compile.cpp:599)
16: vm_compile_method (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/class_support/C_Interface.cpp:2454)
17: DrlEMImpl::methodProfileIsReady(MethodProfile*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/DrlEMImpl.cpp:777)
18: EBProfileCollector::syncModeJitCallback(MethodProfile*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/EBProfileCollector.cpp:191)
19: eb_profiler_sync_mode_callback(void*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/EBProfileCollector.cpp:91)
20: IP is 0xB697503A <native code>
21: ?? (??:-1)
22: gc/Mark.store(Ljava/lang/Object;)I (??:-1)
23: gc/Mark.handle(Ljava/lang/Object;)V (??:-1)
24: gc/Mark.run()V (??:-1)
25: vm_invoke_native_array_stub (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/ia32/base/invoke_native_stub_ia32.asm:41)
26: JIT_execute_method_default(void*, _jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/util/ia32/base/ini_iA32.cpp:199)
27: DrlEMImpl::executeMethod(_jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/DrlEMImpl.cpp:514)
28: ExecuteMethod (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/em/src/em_intf.cpp:43)
29: vm_execute_java_method_array(_jmethodID*, jvalue*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jit/ini.cpp:51)
30: call_method_no_ref_result (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jni/jni_method.cpp:190)
31: CallVoidMethodA(JNIEnv_External*, _jobject*, _jmethodID*, jvalue*) (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/vmcore/src/jni/jni_method.cpp:229)
32: wrapper_proc (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/thread/src/thread_java_basic.c:101)
33: thread_start_proc (/home/dcsfiles/neelakan/Sandbox/Harmony/test/trunk/working_vm/vm/thread/src/thread_native_basic.c:723)
34: dummy_worker (threadproc/unix/thread.c:139)
35: ?? (??:-1)
36: ?? (??:-1)
<end of stack trace>
Segmentation fault
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: http://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466102 ]
Naveen Neelakantam commented on HARMONY-2804:
---------------------------------------------
Thanks Mikhail. I was just curious. :-)
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Minor
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2804?page=comments#action_12460765 ]
Mikhail Fursov commented on HARMONY-2804:
-----------------------------------------
The problem shows that:
1) JIT does not track all hardware exception points correctly
or
2) JIT and GC have misscumminication in GC enumeration
I will take a look at this problem
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: http://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-2804:
----------------------------------------
Assignee: Alexey Varlamov
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Critical
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465680 ]
Naveen Neelakantam commented on HARMONY-2804:
---------------------------------------------
The patch does fix the problem. However, all it does is disable the assert. Is this just covering up a problem, or is the assert itself the bug?
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Critical
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465407 ]
Mikhail Fursov commented on HARMONY-2804:
-----------------------------------------
Naveen,
I've commited a fix for StackTest, please check.
Problem description:
The old GCMap code knows nothing about SOE and contains info only for NPE and calls. When SOE is thrown (arbitrary push op) and GC starts enumeration and GCMap can't find an image for the given IP -> assertion happens -> that was OK before we had SOE handling and this is not correct today.
The patch must fix the problem, however we need to reconsider if we still need to save NPE images in GCMap in debug mode. One of the most important usage scenario of them (the assertion) has gone.
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) StackTest and gc.Mark fail if
vm.jitrino built in debug
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2804?page=all ]
Naveen Neelakantam updated HARMONY-2804:
----------------------------------------
Component/s: DRLVM
> StackTest and gc.Mark fail if vm.jitrino built in debug
> -------------------------------------------------------
>
> Key: HARMONY-2804
> URL: http://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Naveen Neelakantam updated HARMONY-2804:
----------------------------------------
Priority: Minor (was: Critical)
Patch Info: [Patch Available]
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Minor
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466087 ]
Mikhail Fursov commented on HARMONY-2804:
-----------------------------------------
Naveen,
This assertion was used to find the situation when we have GC worked at IP that is neither callsite nor NPE.
When it was written I knew now such situation so the assert was good.
After we added SOE handling any PUSH op can cause GC. So the assert is illegal.
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Minor
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov updated HARMONY-2804:
------------------------------------
Attachment: 2804.diff
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
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] Closed: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov closed HARMONY-2804.
------------------------------------
Resolution: Fixed
Fixed at r500185
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: https://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Assigned To: Alexey Varlamov
> Priority: Minor
> Attachments: 2804.diff
>
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2804?page=comments#action_12460658 ]
Naveen Neelakantam commented on HARMONY-2804:
---------------------------------------------
The patch from Egor Pasko in HARMONY-2805 fixed the gc.Mark issue, however StackTest still fails on RHEL4 update 4.
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: http://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2804) [drlvm][jit] StackTest and gc.Mark
fail if Jitrino built in debug mode
Posted by "Naveen Neelakantam (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2804?page=all ]
Naveen Neelakantam updated HARMONY-2804:
----------------------------------------
Summary: [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode (was: StackTest and gc.Mark fail if vm.jitrino built in debug)
> [drlvm][jit] StackTest and gc.Mark fail if Jitrino built in debug mode
> ----------------------------------------------------------------------
>
> Key: HARMONY-2804
> URL: http://issues.apache.org/jira/browse/HARMONY-2804
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: RHEL4 update 4, gcc 3.4.6, core2 (i386)
> Reporter: Naveen Neelakantam
> Priority: Critical
>
> I am a JIT developer and as a result I generally run DRLVM with jitrino build in debug mode. However, the drlvm tests do not pass in this mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira