Question regarding "native-compiled frame"

[Felix Yang]

Hi,

    Sorry for the late reply. I missed this email.
    Unfortunately, I wasn't able to catch a core dump file of the JVM.
    The hs error log is the same as the one reported on:
https://bugs.openjdk.java.net/browse/JDK-8146224

Thanks.
Felix


On 19 September 2017 at 02:24, Chris Plummer <chris.plummer at oracle.com>
wrote:

> On 9/18/17 7:01 AM, Felix Yang wrote:
>
> Yes, the AArch64 port is doing the same thing as the x86 port.
>
> I noticed this issue when I was trying to analyze a recent JVM crash issue
> which triggers on the x86-64 platform with an official Oracle jdk8u121
> release.
>
> It turns out that this bug happens very rarely (triggered only once for my
> Java workload and I am unable to reproduce it).
>
> And I think it is the same as: https://bugs.openjdk.java.net/
> browse/JDK-8146224 which is still pending there.
>
> Looking at the assembly instructions in the hs error log file, I find the
> SIGSEGV is triggered by the last return statement of frame::sender
> function.
>
> frame::safe_for_sender() is suppose to prevent us from stepping into a
> frame that could result in a JVM crash, even if the frame is corrupted. Do
> you have any additional debugging info, like a gdb stack trace?
>