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] Updated: (HARMONY-5617) [drlvm] On Linux crash handler may crash itself when handling SOE condition
Date Mon, 28 Apr 2008 02:06:59 GMT

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

Ilya Berezhniuk updated HARMONY-5617:

    Attachment: ThreadCreation.gif

Attaching the changes in Thread Manager documentation for suggested approach.

Unfortunately, the problem on Linux still persists. Looks like using shared memory for sharing
global data between several instances of Port static library is not a good idea. Extensive
testing show a cause of problem. 
Both SysV shared memory and memory-mapped files are supposed to be used for inter-process
communication. So these segments remain alive when program exits. The problem appears when
system limit on shared objects is exhausted.
So I need to find another way for sharing global data...

> [drlvm] On Linux crash handler may crash itself when handling SOE condition
> ---------------------------------------------------------------------------
>                 Key: HARMONY-5617
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5617
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>    Affects Versions: 5.0M6
>         Environment: Linux x86 and x86_64
>            Reporter: Gregory Shimansky
>            Assignee: Gregory Shimansky
>            Priority: Minor
>         Attachments: 0001-HARMONY-5617.patch, H-5617-workaround.patch, ThreadCreation.gif,
> When crash handler receives a SIGSEGV signal that is caused by a stack overflow, it tries
to transfer control out of signal handler (just like it does for other kind of signals). But
the problem is that it tries to write memory pointed to by SP register (ESP or RSP) of the
original crash context. When crash happened because of stack overflow, writing to that memory
may not be possible since it is protected by a guard page. In this case crash handler crashes
> Program terminated with signal 11, Segmentation fault.
> #0  0x00002aaaaac27bbf in port_set_longjump_regs (fn=0x2aaaaac2658e, regs=0x7fffbd422b90,
>     at /home/gregory/work/64/trunk/working_vm/vm/port/src/thread/linux/thread_em64t.c:86
> 86          *sp = (void*)regs->rip;
> (gdb) bt
> #0  0x00002aaaaac27bbf in port_set_longjump_regs (fn=0x2aaaaac2658e, regs=0x7fffbd422b90,
>     at /home/gregory/work/64/trunk/working_vm/vm/port/src/thread/linux/thread_em64t.c:86
> #1  0x00002aaaaac26579 in general_signal_handler (signum=11, info=0x7fffbd422d70,
>     context=0x7fffbd422c40)
>     at /home/gregory/work/64/trunk/working_vm/vm/port/src/signals/linux/signals_common.cpp:107
> #2  <signal handler called>
> #3  0x00002aaabf5254c8 in ?? ()
> The crash happens for me on Gentoo Linux installations both on x86 and x86_64. The easiest
way to reproduce it is to run StackTest from the smoke VM tests.

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

View raw message