[cfe-dev] Feature request for 'min/max stack depth option'

[이광무 via cfe-dev]

Hello,

I know there is an option to limit the maximum number of ExplodedNode's, in case the symbolic execution path is getting out of the hands. I tried to increase the limit so that the analyzer can reflect the error context (i.e., stack frame) better, but I turns out this option not necessarily guarantees the extended stack frame context, while the analysis time gets severely delayed.

What I want to propose here is that, instead of arbitrary limiting the number of nodes, limiting the minimum and maximum stack depth of a certain path could enable more accurate analysis (in terms of its error 'context'), while still restricting its resource consumption (including time).

I suppose this is not at all a simple idea (as the error context is unknown before stumbling upon an error while the stack depth is widely varying), I post it here just so that anyone having any idea can propose something when he/she reads this and thinks it's a neat idea.

Thank you,
Gwangmu Lee.


Gwangmu Lee
Ph.D. Student
+82) 10 4114 7441
Room 615, Bldg 301, Gwanak-ro 1, Gwanak-gu, Seoul, South Korea.
http://compsec.snu.ac.kr/~gwangmu<https://link.getmailspring.com/link/7FA96A4B-9CA1-4D33-A75C-C319101053C6@getmailspring.com/0?redirect=http%3A%2F%2Fcompsec.snu.ac.kr%2F~gwangmu&recipient=Y2ZlLWRldkBsaXN0cy5sbHZtLm9yZw%3D%3D>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190305/0b72b0df/attachment.html>