This happens when Klee runs out of file descriptors. You can avoid it by increasing the number of file descriptors using ulimit.
The crash happens because callers of openTestFile do not check if the return is NULL. We encountered this problem before. The attached patch should fix it, in the sense that it avoids crashing and prints a warning instead. If it is ok, I can commit it. Cristi -------------- next part -------------- A non-text attachment was scrubbed... Name: open_test_case.patch Type: application/octet-stream Size: 3903 bytes Desc: not available Url : http://keeda.Stanford.EDU/pipermail/klee-dev/attachments/20100716/9e4060e9/attachment.obj -------------- next part -------------- On Jul 16, 2010, at 5:27 PM, Daniel Dunbar wrote: > Seems like it, yes. Please file a bugzilla if you have a reasonable test case. > > There are cases where KLEE can fail to generate a report (the solver > times out, for example), but it shouldn't crash. > > - Daniel > > On Fri, Jul 16, 2010 at 7:16 AM, heechul Yun <heechul.yun at gmail.com> wrote: >> I ran KLEE to test a http protocol parser. In the middle of symbolic >> execution by KLEE, it gave me the following message and halt. in the output >> directory, only files up to test00031.ktest. >> Is this a bug in KLEE? >> KLEE: ERROR: klee-uclibc/libc/string/strcpy.c:27: memory error: out of bound >> pointer >> KLEE: NOTE: now ignoring this error at this location >> KLEE: WARNING: unable to write output test case, losing it >> KLEE: WARNING: error opening: test000033.ptr.err >> 0 klee 0x08bfb468 >> make: *** [test] Segmentation fault >> -- >> Heechul >> >> _______________________________________________ >> klee-dev mailing list >> klee-dev at keeda.stanford.edu >> http://keeda.Stanford.EDU/mailman/listinfo/klee-dev >> >> > _______________________________________________ > klee-dev mailing list > klee-dev at keeda.stanford.edu > http://keeda.Stanford.EDU/mailman/listinfo/klee-dev
