JDK-6313799 : Long output pathname on windows causes "The system cannot find the path specified" error
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2005-08-20
  • Updated: 2010-04-02
  • Resolved: 2005-08-25
Related Reports
Duplicate :  
Relates :  
Description
The command that fails is
C:\jdk1.5.0\bin\javac -source 1.4 -classpath C:\jdk1.5.0\lib\tools.jar -g -d ..\generated\saclasses <long list of .java file>

The failure occurs when the above compile is done in directory:
      c:/build1234512345678901234567890123456789012345678901234567890/hotspot/windows_i486_compiler2/generated/

The error message is

Z:\xx\tiger-control\hotspot\agent\src\share\classes\sun\jvm\hotspot\debugger\win32\coff\COFFFileParser.java:1202: error while writing <anonymous sun.jvm.hotspot.debugger.win32.coff.COFFFileParser$COFFFileImpl$COFFHeaderImpl$DebugVC50Impl$DebugVC50SrcModLineNumberMapImpl$1>: ..\generated\saclasses\sun\jvm\hotspot\debugger\win32\coff\COFFFileParser$COFFFileImpl$COFFHeaderImpl$DebugVC50Impl$DebugVC50SrcModLineNumberMapImpl$1.class (The system cannot find the path specified)
                public Object computeValue() {

If I shorten that long c:/build.....   pathname by 4 chars (or so), then this error does not occur.

Comments
EVALUATION win32 longpath support has been fixed in mustang, see#6182812, it's no longer reproducible in 6.0, close as "dup of 6182812". The backport to 5.0u has been approved/reviewed.
25-08-2005