JDK-8204648 : test/jdk/tools/launchers/SourceMode.java fails with long shebang line
- Type: Bug
- Component: tools
- Sub-Component: launcher
- Affected Version: 11
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-06-09
- Updated: 2018-06-19
- Resolved: 2018-06-10
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.
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 11 |
|---|
11 b18Fixed  |
Related Reports
|
Relates :
|
Description
When running the test with huge long paths for the launcher, we are running into the silent truncation problem for long shebang lines. The log added by JDK-8204588 shows the warning, and the subsequent truncated filename in the error message. The longest arguments passed to the shebang java is " --source 10 @testBadAtFile/bad.at" (35 chars). We should lower the max tolerated length of javacCmd from 100 to 90.