JDK-8184047 : ExecuteInternalVMTests.java "failed on a valid DirectivesParser string" assert
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: aarch64
  • Submitted: 2017-07-09
  • Updated: 2020-09-01
  • Resolved: 2017-07-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10
10 b21Fixed
Related Reports
Relates :  
Description
In the 2017-07-07 JDK10-hs nightly, the following test:

sanity/ExecuteInternalVMTests.java

failed the following assert():

#  Internal Error (/scratch/opt/jprt/T/P1/164630.iggy/s/hotspot/src/share/vm/compiler/directivesParser.cpp:573), pid=11927, tid=11930
#  assert(cd.valid() == true) failed: failed on a valid DirectivesParser string
#
# JRE version: Java(TM) SE Runtime Environment (10.0) (fastdebug build 10-internal+0-2017-07-07-164630.iggy.8183991)
# Java VM: Java HotSpot(TM) Client VM (fastdebug 10-internal+0-2017-07-07-164630.iggy.8183991, mixed mode, serial gc, linux-)

This is very strange, but the crashing thread has no stack:

---------------  T H R E A D  ---------------

Current thread (0xf6811800):  JavaThread "main" [_thread_in_vm, id=11930, stack(0xf6916000,0xf6966000)]

Stack: [0xf6916000,0xf6966000]

---------------  P R O C E S S  ---------------

Java Threads: ( => current thread )
  0xeb386400 JavaThread "Service Thread" daemon [_thread_blocked, id=11961, stack(0xeb760000,0xeb7b0000)]
  0xf68df800 JavaThread "Common-Cleaner" daemon [_thread_blocked, id=11950, stack(0xeb7b0000,0xeb800000)]
  0xf68b7400 JavaThread "Sweeper thread" daemon [_thread_blocked, id=11946, stack(0xeb930000,0xeb980000)]
  0xf68b5800 JavaThread "C1 CompilerThread0" daemon [_thread_blocked, id=11945, stack(0xeb980000,0xeba00000)]
  0xf68afc00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=11944, stack(0xebd10000,0xebd60000)]
  0xf689b800 JavaThread "Finalizer" daemon [_thread_blocked, id=11939, stack(0xebd60000,0xebdb0000)]
  0xf6898000 JavaThread "Reference Handler" daemon [_thread_blocked, id=11938, stack(0xebdb0000,0xebe00000)]
=>0xf6811800 JavaThread "main" [_thread_in_vm, id=11930, stack(0xf6916000,0xf6966000)]

Other Threads:
  0xf6899c00 VMThread "VM Thread" [stack: 0xebf34000,0xebfb4000] [id=11935]
  0xeb388c00 WatcherThread [stack: 0xeb280000,0xeb300000] [id=11962]
Comments
VectorizeDebug is defined inside #ifdef COMPILER2, so it won't be recognized in a -client build.
24-07-2017

This reported JDK-8184047 nightly failures started after JDK-8183271 fix commit.
12-07-2017

Hi Nils, could you please have a look? Thanks, Tobias
12-07-2017

ILW = Crash with ExecuteInternalVMTests, Assert failure in DirectivesParser_test internal test; 1 unit test, only in Linux-AArch64, with -client; use product build or disable ExecuteInternalVMTests = HLM = P3
10-07-2017