RFR(s): 8065895: Synchronous signals during error reporting may terminate or hang VM process
Thomas Stüfe
thomas.stuefe at gmail.com
Thu Nov 27 10:38:49 UTC 2014
Hi Andrew, thank you! Does endianess matter ?
On Thu, Nov 27, 2014 at 10:45 AM, Andrew Haley <aph at redhat.com> wrote:
> On 11/27/2014 09:01 AM, David Holmes wrote:
> > On 27/11/2014 5:36 PM, Thomas Stüfe wrote:
> >> Unfortunately, I cannot test it, as I have no ARM environment. The best
> >> I can come up with without testing is this:
> >>
> http://stackoverflow.com/questions/16081618/programmatically-cause-undefined-instruction-exception
> >
> > The issue is how to handle this? Put ifdefs for ARM in the open code?
> > Revert to your per-platform solution? Some other variation? Or do we
> > just not care if we can't trigger SIGILL on ARM? Though I'd like to hear
> > from the AARCH64 folk too.
>
> I always use DCPS1 if I want an undefined instruction trap. 0x0100A0D4.
>
> Andrew.
>
>
>
More information about the hotspot-runtime-dev
mailing list