Segfault when running compiled Truffle method.

[Wei Zhang]

Hi,

The error log was dropped by the mailing list.
I uploaded it to here:
https://db.tt/SnWrKZ3I

Thanks,
/Wei


On Tue, Jan 21, 2014 at 7:41 PM, Wei Zhang <ndrzmansn at gmail.com> wrote:
> Hi,
>
> I keep ran into the same crash when I try run a couple of benchmarks on ZipPy.
>
> The benchmarks that I have problem with are Python generator
> intensive, which relies heavily on MaterializedFrames.
> I believe it has something to do with compiled code that accesses
> MaterializedFrame.
> Sometime, com.oracle.truffle.api.impl.DefaultMaterializedFrame::setInt
> shows up in the error message.
>
> The error message:
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x0000000107a06c0b, pid=40193, tid=6403
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
> # Java VM: OpenJDK 64-Bit Server VM (25.0-b63-internal mixed mode
> bsd-amd64 compressed oops)
> # Problematic frame:
> # J -1 Graal com.oracle.graal.truffle.OptimizedCallTarget.executeHelper(Lcom/oracle/truffle/api/frame/PackedFrame;Lcom/oracle/truffle/api/Arguments;)Ljava/lang/Object;
> (22 bytes) @ 0x0000000107a06c0b [0x0000000107a06800+0x40b]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /Users/zwei/Workspace/zippy/hs_err_pid40193.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.sun.com/bugreport/crash.jsp
> #
>
> The error log is attached.
>
> The problem can be reproduced with this command:
> ./mx.sh --vm server python
> graal/edu.uci.python.benchmark/src/benchmarks/bm-ai.py @-esa @-ea
>
> The latest commits of zippy can be pulled from:
> ssh://hg@bitbucket.org/ssllab/zippy
>
> I'm not sure what would be the best way to debug this from my side,
> since it went through the entire compilation phases and crashed at
> runtime.
> Does anybody has experienced the similar problem?
> Any help is appreciated.
> Thanks,
>
> /Wei