Re: [klee-dev] segmentation fault

On 23 September 2016 at 23:43, Reza Ahmadi wrote: > Hi all, > > I tried to run a simple .cpp code using Klee. My code includes some > float-related operations. If I remove the float-related stuff, then, Klee is > successful in generating 3 test cases but fails if I include

[klee-dev] segmentation fault

Hi all, I tried to run a simple .cpp code using Klee. My code includes some float-related operations. If I remove the float-related stuff, then, Klee is successful in generating 3 test cases but fails if I include float things. My questions (sorry if too stupid, I am new to Klee): 1- Is Klee

[klee-dev] Segmentation fault when testing Flex

Hi all, I am not sure if this would be a bug in KLEE - it calls an external longjmp and then a segmentation fault happens. I ran KLEE on Flex like so: $ klee -max-time=30 -libc=uclibc --posix-runtime flex.bc KLEE: NOTE: Using klee-uclibc : /usr/lib/klee/runtime/klee-uclibc.bca KLEE: NOTE: Using

[klee-dev] Segmentation fault

Hello, every one: Recently, I am working on using KLEE with BAP, a binary analysis platform that can generate LLVM bitcode. When I try to use KLEE to analyze the LLVM bitcode generated by BAP, I encountered with several problems: The test source code is quite simple. When I compile it into

[klee-dev] Segmentation fault

Hi Cristi, That's a rather minor thing, but instead of having all the callers of openTestFile (and openOutputFile) call klee_error or assert, I would just call klee_error directly in openOutputFile. Let me know if you see any problems in the attached patch. Thanks, Cristian On 25/07/10

[klee-dev] Segmentation fault

Thanks, Cristi, that's a very good idea. I added this and applied the patch in 110329. Best, Cristian On 05/08/10 10:57, Cristian Zamfir wrote: Hi Cristi, Indeed, if we call klee_error instead of klee_warning, there is no point in calling it from everywhere. I didn't test, but the patch

[klee-dev] Segmentation fault

I tried klee --libc=uclibc -max-memory=48 --only-output-states-covering-new httpd.bc terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc 0 klee 0x08bfcfc8 Aborted On Sun, Jul 25, 2010 at 2:20 PM, Cristian Zamfir cristian.zamfir at epfl.chwrote: This

[klee-dev] Segmentation fault

Sorry, the previous mail was mistakenly sent in the middle of writing. I tried both with/without -max-memory=64, but they all gave me the same result. Stack trace at the fault is the following. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Program

[klee-dev] Segmentation fault

Hi Cristi, You are right, I doubt that the reasons for running out of fds are transient, so it is better to stop. I modified the patch. -- next part -- A non-text attachment was scrubbed... Name: failed_test_case.patch Type: application/octet-stream Size: 3889 bytes

[klee-dev] Segmentation fault

I think there is a mistake. Please see the red lines of your patch. if (WriteTestInfo) { double elapsed_time = util::getWallTime() - start_time; std::ostream *f = openTestFile(info, id); if(f) { *f Time to generate test case: elapsed_time s\n; delete f; * }* *

[klee-dev] Segmentation fault

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-dev] Segmentation fault with iostream

Hi Seungbeom, On Fri, Jun 4, 2010 at 4:10 PM, Seungbeom Kim sbkim at stanford.edu wrote: Hi, I find that #include iostream alone causes KLEE to segfault at the end of the run, but not with --libc=klee or --libc=uclibc. First, let me start by saying that trying to run KLEE on C++ code isn't

[klee-dev] Segmentation fault with iostream

Hi, I find that #include iostream alone causes KLEE to segfault at the end of the run, but not with --libc=klee or --libc=uclibc. $ cat header.cc #include iostream int main(int, char**) { } $ klee --libc=none header.o ... KLEE: done: total instructions = 39 KLEE: done: completed paths = 1