News for hackers. Stuff that matters.
Re:SLAyer by akavel on Wednesday May 04, 2016 @10:23AM (#11628550)
Is anyone aware what are the tool's limitations? Seems open-sourced ~1-2 months ago already, with publications history spanning much longer [1], but the README is very sparse, and I wouldn't probably understand much if I tried to dive into the research papers. Or am I to believe it will find 100% all memory issues?

[1]: http://research.microsoft.com/en-us/projects/slayer/

Re:SLAyer by saminishtiaq on Wednesday May 04, 2016 @12:16PM (#11629388)
It's a static analysis tool, so it has many TimeOut limitations :-) In practise, many abstract interpretation based tools generalize too much, lose too much information, then get lost and TO instead. The test suite released there gives a good empirical idea of what SLAyer can do. You'll see lots of while-loops over single- and doubly-linked lists as SLAyer can generalize Separation Logic points-to predicates to 'sll' list predicates.
Re:SLAyer by akavel on Thursday May 05, 2016 @10:58AM (#11636649)
I'm specifically interested here in what the tool cannot do, more than what it can do. For now all I can tell is it "works for some empirical cases, and maybe works in rest of cases, but not strictly defined, don't expect anything concrete".