-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
occasional crashes #11
Comments
Thanks for raising the issue, |
I don't have any such file even in the successful workdirn directories. The directory listing of a "good" workdirn:
And one of the failures:
|
Ah, sorry I mixed up names, it should be forward.log |
No problem. I can just include that here due to its small size.
|
Ah, that is a surprising failure that I haven't seen before. |
Hi,
First of all, I want to thank you for this program. I recently finished a paper for school that required the creation of over two dozen collisions.
On a few (maybe three) of those, the program simply died at some point. It appears that the program did not create workdirn/paths10_0of1.bin.gz and workdirn/paths11_0of1.bin.gz
This led to the following message in workdirn/connect.log:
I have no idea why this happened, but I have saved the entire output directory (about 350 MB compressed) of one of the failures, including the failed workdirs (which I renamed), in case you need any information from them.
Thanks again.
The text was updated successfully, but these errors were encountered: