harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1912) [drlvm][jit][opt] SIGSEGV during stack dump on Linux
Date Mon, 12 Mar 2007 13:15:09 GMT

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

Ilya Berezhniuk commented on HARMONY-1912:
------------------------------------------

I've updated the patch; new version contains following changes since previous version:

1) Check for recursive crash was added for Windows, so AbstractPreferencesTest  is passed
in release build.

While executing this test, C heap are exhausted, and crash handler tries to print stack trace.
When crash handler tries to get 'vm.assert_dialog' property, it involves memory allocation
attempt. So VM was dropped to crash handler again, and again.

2) native_stack_em64t.cpp was filled in with stack unwinding helper functions. Unfortunately,
Microsoft compiler does not create stack frames on Windows/em64t, so native stack is empty.
But on Linux/em64t native stack is obtained successfully.

I've checked, on both Windows/ and Linux/em64t Java source lines are now represented as (-1),
even without this patch. So this problem can be reported in separate JIRA.

> [drlvm][jit][opt] SIGSEGV during stack dump on Linux
> ----------------------------------------------------
>
>                 Key: HARMONY-1912
>                 URL: https://issues.apache.org/jira/browse/HARMONY-1912
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: SUSE9
>            Reporter: Alexey Varlamov
>         Assigned To: Alexey Varlamov
>            Priority: Minor
>         Attachments: 1912_workarround.patch, crash_handler.diff, crash_handler.diff,
crash_handler.diff, log_lnx_ia32_after.txt, log_lnx_ia32_before.txt, log_win_ia32_after.txt,
stack_test.zip
>
>
> There is some issue in StackInfo, manifesting itself as a segmentation fault during stack
dump.
> For example, see HARMONY-1911, HARMONY-1908, HARMONY-1908, HARMONY-1905.
> Typical backtrace is as follows:
> SIGSEGV in VM code. 
> Stack trace: 
> 41: Jitrino::Ia32::StackInfo::readByteSize(unsigned char const*) const (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/jitrino/src/codegenerator/ia32/Ia32StackInfo.cpp:107)

> 42: Jitrino::Ia32::RuntimeInterface::getBcLocationForNative(Jitrino::MethodDesc*, unsigned
long long, unsigned short*) (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/jitrino/src/codegenerator/ia32/Ia32RuntimeInterface.cpp:78)

> 43: Jitrino::Jitrino::GetBcLocationForNative(Jitrino::MethodDesc*, unsigned long long,
unsigned short*) (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/jitrino/src/main/Jitrino.cpp:358)

> 44: get_bc_location_for_native (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/jitrino/src/vm/drl/DrlJITInterface.cpp:590)

> 45: Dll_JIT::get_bc_location_for_native(Method*, void*, unsigned short*) (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/vmcore/include/dll_jit_intf.h:240)

> 46: get_file_and_line (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/vmcore/src/stack/stack_trace.cpp:60)

> 47: st_get_java_method_info (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/vmcore/src/stack/stack_dump.cpp:196)

> 48: st_print_stack(Registers*) (/export/users2/avarlamo/linux.ia32/svn-repo/drlvm/vm/vmcore/src/stack/stack_dump.cpp:242)


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