JPackage does very weird things and it doesn't work with SNAP

David Holmes david.holmes at oracle.com
Mon Dec 9 05:14:06 UTC 2024


On 9/12/2024 1:21 pm, David Alayachew wrote:
>  > If it's one
> of the expected ones, things will proceed normally.
> 
> There are expected segfaults in libjvm?
> 
> Sorry, I am 100% ignorant about this subject. I just wanted to know if 
> that was the intended meaning.

Yes there is a deliberate segfault during VM startup to check AVX 
register save/restore behaviour. An optional one (non-product) for APX 
register save/restore behaviour.

David
-----

> 
> On Sun, Dec 8, 2024, 3:46 PM Kim Barrett <kim.barrett at oracle.com 
> <mailto:kim.barrett at oracle.com>> wrote:
> 
>     On 12/8/24 1:56 PM, Davide Perini wrote:
>      > I tried attaching gdb, but it’s clear that jvm doesn’t like
>     debuggers
>      > attached. Right from the start it got sigstop handlers invoked, and
>      > then a segfault in libjvm.
> 
>     I can't comment on the rest of your message, but I might be able to
>     help
>     with
>     this. The JVM sometimes executes code that may trigger signals that are
>     expected to be handled by the JVM's signal handler. In particular, I
>     know
>     there are a couple of these early in startup. Just try continuing in the
>     debugger, and let the JVM's signal handler have a crack at them. If
>     it's one
>     of the expected ones, things will proceed normally.
> 



More information about the core-libs-dev mailing list