Svadev mailing list

[Vikram Adve <vadve AT illinois.edu>]

SAFECode does NOT *detect* use-after-free errors, in normal operation.  
Instead, it "tolerates" those errors in the sense that it allows such errors 
to occur but guarantees that none of the other memory safety properties will 
be violated as a side effect of the error.  See our PLDI 2006 paper (on the 
SAFECode Web site) for how we do that.

We did have debug support to detect those errors in the debug version.  I 
don't know if that is in mainline, and if so, if it is turned on by default 
or not.

--Vikram
Professor, Computer Science
University of Illinois at Urbana-Champaign
http://llvm.org/~vadve




On Sep 27, 2012, at 1:50 PM, Santosh Nagarakatte 
<santosh.nagarakatte AT gmail.com>
 wrote:

> Hi all,
> 
> I was wondering how SAFECode detects use after free errors.  There are
> many use-after-free tests in tests directory.
> I did a quick scan of the safecode source code. I could not find
> specific checks that performed use-after-free checking.
> Can you point me to documentation that describes how use-after-free
> errors are detected with SAFECode?
> 
> Are all the use-after-errors detected by Valgrind or ASan also
> detected by SAFECode's use after free checking?
> 
> Thanks,
> Santosh
> 
> -- 
> Santosh G Nagarakatte,
> Computer and Information Science Department
> University of Pennsylvania,
> Philadelphia-19104
> http://www.cis.upenn.edu/~santoshn
> _______________________________________________
> svadev mailing list
> svadev AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/svadev