SIGSEGV on PhaseIdealLoop::split_up?

[Tobias Hartmann]

Hi Uwe,

I've filed https://bugs.openjdk.java.net/browse/JDK-8218067 for this issue.

Thanks,
Tobias

On 30.01.19 15:51, Uwe Schindler wrote:
> Hi,
> 
> as many of you know: I have no access to the OpenJDK bugtracker. I am currently on travel, but later today, I'd take the current problem and I may open a new bug in the OpenJDK issue tracker about this issue. The stack traces all look very similar, so there should be enough information to figure out where exactly the SIGSEGV is happening. To my knowledge of development, this should help to get the condition, why this is happening. Together with the Lucene Source code, you may figure out the conditions. Because this bug is quite new, there must be some change in Lucene that triggers this bug. With the information about where the SIGSEGV is happening in OpenJDK code and the commit logs in Lucene, we may figure out how the Lucene code changed so it causes that issue.
> 
> I will take the time and try to collect all information an OpenJDK developer needs to (hopefully) reproduce the issue.
> 
> Does this sound like a plan?
> Uwe
> 
> -----
> Uwe Schindler
> uschindler at apache.org 
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> http://lucene.apache.org/
> 
>> -----Original Message-----
>> From: hotspot-dev <hotspot-dev-bounces at openjdk.java.net> On Behalf Of
>> Dawid Weiss
>> Sent: Wednesday, January 30, 2019 10:28 AM
>> To: hotspot-dev <hotspot-dev at openjdk.java.net>
>> Subject: SIGSEGV on PhaseIdealLoop::split_up?
>>
>> Hello,
>>
>> There's quite a few of those JVM errors that popped up recently on one
>> of Lucene's CI machines:
>>
>> https://issues.apache.org/jira/browse/LUCENE-8668
>>
>> Happens on various JVMs (see the above issue). Would it be something
>> familiar to any of you? A known issue or should we try to keep digging
>> (for a repro, for example)?
>>
>> Dawid
>