harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4265) [drlvm][jit] Save quantity of try and catch blocks equals.
Date Thu, 24 Jan 2008 11:51:35 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562020#action_12562020
] 

Gregory Shimansky commented on HARMONY-4265:
--------------------------------------------

Yes, I can't reproduce this any more on Linux x86. But on Linux x86_64 the test still crashes
pretty well. This time the crash happened in threading library because hythread_thin_monitor_try_enter
is called with some bad lockword that cannot be found in fat monitors array. Stack looks like
this:

(note crash handler crashes too, so don't look at crash handler's stack frames after <signal
handler called>

#0  0x00002aaaaab14b16 in Class_Member::is_static (this=0x0) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/include/class_member.h:72
#1  0x00002aaaaabf9a45 in Method::get_num_args (this=0x0) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/class_support/method.cpp:261
#2  0x00002aaaaabb099a in get_jvalue_arg_array (method=0x0, args=0x7fffa33cd8d0) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/jni/jni_utils.cpp:98
#3  0x00002aaaaabae3ce in CallObjectMethodV (jni_env=0x1054930, obj=0x104cfc0, methodID=0x0,
args=0x7fffa33cd8d0) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/jni/jni_method.cpp:248
#4  0x00002aaaaabe0e5b in JNIEnv_External::CallObjectMethod (this=0x1054930, obj=0x104cfc0,
methodID=0x0) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/include/jni.h:731
#5  0x00002aaaaac1e8bb in sd_print_threads_info (cur_thread=0x549a80) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/stack/stack_dump.cpp:394
#6  0x00002aaaaac1f410 in sd_print_stack (regs=0x7fffa33cdb00) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/stack/stack_dump.cpp:433
#7  0x00002aaaaac1d0f0 in process_crash (regs=0x7fffa33cdb00) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/util/linux/ia32_em64t/signals_common.cpp:500
#8  0x00002aaaaac1d164 in general_crash_handler (signum=11, regs=0x7fffa33cdb00, message=0x2aaaaad81476
"SIGSEGV") at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/util/linux/ia32_em64t/signals_common.cpp:513
#9  0x00002aaaaac1d981 in null_java_reference_handler (signum=11, info=0x7fffa33cdd70, context=0x7fffa33cdc40)
at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/util/linux/ia32_em64t/signals_common.cpp:439
#10 0x00002aaaaac1db01 in general_signal_handler (signum=11, info=0x7fffa33cdd70, context=0x7fffa33cdc40)
at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/vmcore/src/util/linux/ia32_em64t/signals_common.cpp:558
#11 <signal handler called>
#12 0x00002b0207053c8a in locktable_get_fat_monitor (lock_id=Cannot access memory at address
0x7fffa2bceff8
) at /nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/thread/src/thread_native_thin_monitor.c:822
#13 0x00002b02070528b3 in hythread_thin_monitor_try_enter (lockword_ptr=0x2aaaae299330) at
/nfs/ims/proj/drl/mrt2/users/gregory/em64t/trunk/working_vm/vm/thread/src/thread_native_thin_monitor.c:366
#14 0x00002aaaac642873 in ?? ()


> [drlvm][jit] Save quantity of try and  catch blocks equals.
> -----------------------------------------------------------
>
>                 Key: HARMONY-4265
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4265
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Assignee: Mikhail Fursov
>         Attachments: soe2.patch
>
>
> To save quantity of try and  catch blocks equals JIT support is required. 
> If JIT compile method which contains SOE exception handler, it should include test of
avalable stack inside  method code.

-- 
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