Random SIGSEGV when running benchmark with perfasm - JMH, hsdis or JVM issue?

[Aleksey Shipilev]

What Nitsan said.

You can report it to bugs.java.com, but it would be handier if you could add the
basic information here. The stack trace and the hs_err might be revealing.

-Aleksey

On 06/14/2017 09:59 AM, Nitsan Wakart wrote:
> Hi,Please include basic information:- A link to the hs_err file(post it somewhere if you can)- A link to your original email- Versions: OS/JVM/hsdis- HWThanks,Nitsan 
> 
>     On Wednesday, June 14, 2017 9:22 AM, Bartosz Skrzypczak <barteks2x at gmail.com> wrote:
>  
> 
>  I already talked about it when I asked about "Random
> java.util.NoSuchElementException exceptions when using perfasm"
>  back in january 2017.  I know this is probably not the right place to
> ask but I don't have any better idea. I think it may be the same
> crash, but it was so long ago that I'm not sure. I am able to
> reproduce it only with JMH with perfasm on my project so far, and is
> uses hsdis, which means it may not necessarily be JVM issue. And I'm
> profiling the same code part of code (a big part of code) as back
> then. The problematic frame I'm getting is "V  [libjvm.so+0x8e095d]
> Monitor::lock_without_safepoint_check()+0x3d".
> 
> I'm not really sure where I should even report it. I just happened to
> get a core dump from it so this is the first time I may have enough
> information to actually report it somewhere.
> 
> Could I get some information as to what would be the appropriate place
> to report it?
> 
> 
>    
>