-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCDD exception while unable to open log file #59
Comments
I need some more information - I'm unable to duplicate the problem. Java version? OS? Command line options? Is your hard drive full? ;^) Another thought: If the file path is null the file pointer ends up null as well and will produce the error you're seeing. If you don't have access to the backing store (where the preferences are stored) that may can cause this issue. |
Java: 1.8.0_201 (64-bit), Win10. Plenty of space on the harddrive, and we were able to reproduce this on two win10 machines. Command:
where the logPath is any path on my machine. Testing each of the recent commits, I find that this starts occurring in 1.4.80 which does mention changes to file path handling in the commit message. |
Thanks - I found the problem. It's odd that it doesn't affect Linux. It may be Monday morning before I can upload the corrected version. |
in Pattern.quote() when used in the regular expression (Github issue #59). Added the -nottimestamp option when creating the Javadoc (the eliminates the time stamps and makes locating differences between old and new Javadoc files easier; Github issue #60). Added the javadoc.xml Ant script. Updated Javadoc and CCDD.jar (version 1.4.97).
Corrected in version 1.4.97. |
I'm unable to launch newer versions of CCDD. The following exception is observed on version 1.4.96:
logPath argument is the same that I've been using previously and I've confirmed that the folder exists (and is populated with log files from prior versions), so I don't see any reason that it should be unable to create the log file. The exception is the same whether the
-shutdown
argument is provided or not, despite the event log window (referenced in the stack track) not being present when the GUI is not shown.I had upgraded from version 1.4.79 and on that version if the path doesn't exist it will emit
but still launch CCDD.
The text was updated successfully, but these errors were encountered: