[klee-dev] Possible improvement for --write-paths
Alberto Barbaro
barbaro.alberto at gmail.com
Sun Mar 4 08:44:04 GMT 2018
The Cristian,
honestly I was think about something with a different structure. Maybe
something like:
<path>
<nodes>
<node id=1 address="0x...." other_attribute="node_1"
successor="2">.....</node>
<node id=2 address="0x...." other_attribute="node_2"
successor="3">.....</node>
....
<nodes>
</path>
Of course the path should track also intra-procedural calls and all the
other calls/returns/...
Do you think it would useful?
Thanks
2018-03-03 21:10 GMT+00:00 Cristian Cadar <c.cadar at imperial.ac.uk>:
> Hi, there in an open PR about this, which you might like to use, although
> it still requires some work: https://github.com/klee/klee/pull/473
>
> Best,
> Cristian
>
>
> On 03/03/2018 08:06, Alberto Barbaro wrote:
>
>> Hi again,
>> I have seen that it is possible to save the paths using the option
>> --write-paths, the output contains a lot of 0 and 1 which I guess are the
>> result for branches. Is it possible to have a more verbose output
>> containing for example the list of addresses encountered? If so, can I have
>> an idea on how to do it please?
>>
>> Thanks
>>
>>
>> _______________________________________________
>> klee-dev mailing list
>> klee-dev at imperial.ac.uk
>> https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
>>
>>
> _______________________________________________
> klee-dev mailing list
> klee-dev at imperial.ac.uk
> https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
>
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the klee-dev
mailing list