Open nickdesaulniers opened 5 years ago
Thanks! This symptom seems like something I haven't seen before, but I've long suspected there's a race or two somewhere in C-Reduce that I've not managed to track down. I'll take another look at some point but not in the next few weeks.
cool blog post!
Hit a similar thing today running with 32 threads:
cannot copy '/usr/local/google/home/blaikie/dev/scratch/creduce/mod_mutex/mutex.h' at /usr/local/google/home/blaikie/dev/creduce/build/creduce/creduce line 308. at /usr/local/google/home/blaikie/dev/creduce/build/creduce/creduce line 35. main::ANON("cannot copy '/usr/local/google/home/blaikie/dev/scratch/credu"...) called at /usr/local/google/home/blaikie/dev/creduce/build/creduce/creduce line 308 main::copy_files_here() called at /usr/local/google/home/blaikie/dev/creduce/build/creduce/creduce line 621 main::delta_pass(HASH(0x556fe7a772f0)) called at /usr/local/google/home/blaikie/dev/creduce/build/creduce/creduce line 1067
Not sure if there's anything especially useful I can provide/do to help debugging this.
argh! thanks David. I guess I just need to review the threading logic again, this is hard enough to repro that I don't think any other debugging method will get it.
Hmm - I realized my /tmp is on a relatively small drive - so a second run hit a "not enough space on device" error. Possible that the previous error was related to that but just with a slightly different failure mode?
I'm running with a bigger /tmp - well... I thought I was, but seems I'm not. Not sure how to tell creduce to use a different temp directory. But I reduced the amount of space my test script uses, so maybe that'll be enough.
Looks like maybe some kind of race when copying a file?
Also, thanks for such a great tool: https://nickdesaulniers.github.io/blog/2019/01/18/finding-compiler-bugs-with-c-reduce/