SIGSEGV on PhaseIdealLoop::split_up?

[Uwe Schindler]

Hi Alexey,

I will be on FOSDEM and we can for sure meet on Saturday. Latest at dinner! I am also in Brussels on Monday, so if we need more time we can maybe meet at Monday after-FOSDEM unconference.

Uwe

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: uwe at thetaphi.de

> -----Original Message-----
> From: hotspot-dev <hotspot-dev-bounces at openjdk.java.net> On Behalf Of
> Aleksey Shipilev
> Sent: Wednesday, January 30, 2019 11:51 AM
> To: Dawid Weiss <dawid.weiss at gmail.com>; Nils Eliasson
> <nils.eliasson at oracle.com>
> Cc: hotspot-dev <hotspot-dev at openjdk.java.net>
> Subject: Re: SIGSEGV on PhaseIdealLoop::split_up?
> 
> On 1/30/19 11:43 AM, Dawid Weiss wrote:
> > Current CompileTask:
> > C2:1534619 50541  s!   4
> > org.apache.lucene.index.ConcurrentMergeScheduler::merge (280 bytes)
> >
> > The path leading to it may differ (when you diff those different
> > hs_err logs against each other), but it seems to be caused by merge
> > compilation in all cases I looked at.
> 
> This is release build, right? fastdebug build probably asserts somewhere?
> 
> > I can monitor this and attach new logs to the Jira issue
> > (LUCENE-8668). Uwe will be at Fosdem so I'm sure he'll be ready to
> > figure it out together with you, should you be there.
> 
> If Nils is not there, let Uwe find me at FOSDEM?
> 
> -Aleksey