From c.cadar at imperial.ac.uk Wed Jan 4 13:09:11 2023 From: c.cadar at imperial.ac.uk (Cristian Cadar) Date: Wed, 4 Jan 2023 13:09:11 +0000 Subject: [klee-dev] Debugging options In-Reply-To: References: Message-ID: <617b998b-c76c-ffd2-7b8a-198c442946e1@imperial.ac.uk> On 22/12/2022 16:09, Muralee, Siddharth wrote: > Hello, > > I am currently working on a project to verify states that end due to > errors such as "memory error: out of bound pointer". Currently, I am > trying to extract some information about these states, and the most > information I am able to extract is the instruction log from replaying > only the seed file, using the options |--debug-print-instructions|? and > |--only-seed --seed-file|??. > > Is there any way to extract more details? While running an application > with a seed input. What other info would you like? Most likely you would need to add support for additional info yourself. > Also, for the |debug-print-instructions=all:stderr|? is there any way to > restrict Klee from printing all the instructions inside the libraries? > It takes an insane amount of time looping inside the runtime setup code > as well as library functions such as sprintf etc. There are no options to do so, but this could be easily accomplished by changing the code. To reduce the amount of logged data, you could use --debug-compress-instructions, which compresses the logged instructions in gzip format. Best, Cristian From btssrikar at gmail.com Mon Jan 9 10:42:15 2023 From: btssrikar at gmail.com (Teja Sai Srikar Bodavula) Date: Mon, 9 Jan 2023 16:12:15 +0530 Subject: [klee-dev] General question Message-ID: Hello, I was wondering if there is way in which we can get symbolic formula for a variable in a code in smt2 format unlike kquery format which we get using klee_print_expr. -------------- next part -------------- HTML attachment scrubbed and removed