Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <18908453.1173085911562.JavaMail.jira@brutus>
Date: Mon, 5 Mar 2007 01:11:51 -0800 (PST)
From: "Ilya Berezhniuk (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-1912) [drlvm][jit][opt] SIGSEGV during
 stack dump on Linux
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ilya Berezhniuk updated HARMONY-1912:
-------------------------------------

    Attachment: crash_handler.diff

The updated patch with new crash handler implementation.

The main improvements made since last patch:

1) Patch was updated to reflect changes made for Windows/em64t.
2) get_inlined_bc() function was added to JIT external interface; corresponding stubs and wrappers were created.
3) LOGGER_EXIT() macro was added to clog.h
4) Inline methods processing using get_inlined_bc() function was added into get_file_and_line() function. Inline depth was added as a parameter for function, and as a field in StackTraceFrame structure.
5) Stack dump printing was enabled for Linux/em64t in case of crash.
6) Register state printing on Win/em64t was corrected.

> [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, 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.