Running Windows 7, JRE 1.6.0_17. Reproduced this with Proguard 4.4 and 4.5beta2.
From the "%PROGUARD_HOME%\bin" directory, run the command "proguard.bat -injar nonExistantFile".
The result is:
ProGuard, version 4.5 beta2
Reading program directory [C:\Program Files\Proguard\bin\nonExistantFile]
Error: Can't read [proguard.ClassPathEntry@c4bcdc] (No such file or directory)
This error message is displayed because the injar does not exist. However, at first glance, it appeared to me as though Proguard itself were broken due to some compilation or classpath issue.
I'm guessing that the error message is intended to print the path to the missing file. The toString() method of the proguard.ClassPathEntry class could be overridden to return this information.
Thanks for the report. I had accidentally removed the toString method in version 4.4. The bug has recently been fixed for the upcoming version 4.5 beta3.