I hit two more crashes. FYI crash-files attached. They looks very similar.
Thanks, Dmitry 2013/6/9 Yang Chen <[email protected]>: > I think it's clang_delta bug. I will investigate it. Thanks for the > feedback! > > - Yang > > > On 6/8/13 2:58 PM, Дмитрий Дьяченко wrote: >> >> John, >> with creduce-latest + clang-3.2 I got the same crash in test #6. >> Now I find crash-file in temporary directory in creduce/tests/ >> Crash-file attached. >> >> Sorry, I not mention early why I try clang-latest + creduce-latest: at >> first, to my fun :), and second, in hope to provide useful feedback to >> your research group. >> I do gcc-bug-hunting relatively rare and for each new one I try new >> clang + new creduce :) >> >> May be you find interesting [preliminary] comparison of >> creduce-current with clang-3.2/3.4-trunk >> >> 1. comparison creduce/tests/run_tests >> a) the same tests FAIL and PASS >> b) test #6 crash with both clang's versions >> c) elapsed time in seconds as run_tests reports >> 3.2 3.4-current >> 0: 922 207 >> 1: 23 28 >> 2: 928 212 >> 3: 17 24 >> 6: 2209 1048 >> >> 2. comparison for real-world tasks: >> results are identical with both versions of clang -- reductions hang >> >> Thanks, >> Dmitry >> >> 2013/6/8 John Regehr<[email protected]>: >> >>> >>> Hi Dmitry, >>> >>> I'm in the middle of some more C-Reduce changes right now. It might be >>> best >>> to not use the current version until things stabilize a bit. >>> >>> >>> >>>> >>>> -- tests 0..3 PASS >>>> -- tests 4, 5, 7 FAIL with >>>> >>> >>> >>> I'll look into this, thanks for letting us know. >>> >>> >>> >>>> >>>> 0.<eof> parser at end of file >>>> sh: line 1: 23784 Segmentation fault (core dumped) >>>> /home/dimhen/build/creduce/creduce/../clang_delta/clang_delta >>>> --transformation=return-void --counter=1 >>>> /home/dimhen/tmp/creduce-WStouG/small.c> /tmp/file0I5kCp >>>> >>> >>> >>> Right now we only develop and test using Clang 3.2, so we can't help you >>> with crashes against the LLVM top of tree. It's super easy to download >>> the >>> 3.2 binary distribution and compile C-Reduce against it, so I'd ask you >>> to >>> just do that. >>> >>> I have not seen any hangs like you are seeing, but it could easily be >>> that I >>> have introduced new bugs lately. I'm still making some changes to the >>> core >>> of C-Reduce but will hopefully be done soon, and then I'll try to >>> reproduce >>> the problems you are seeing. >>> >>> John >>> > >
clang_delta_crash_tmp_fileA0BcyX.i
Description: Binary data
clang_delta_crash_tmp_fileCKvCPy.i
Description: Binary data
