Re: [csmith-dev] feature request: generate memory unsafe code

["Xuejun Yang" <jxyang@cs.utah.edu>]

Pointer unsafe behaviors are allowed in Csmith (git commit 7e3325). I am
adding array OOB soon. The two command line options are exactly what you
requested:

--null-ptr-deref-prob <N> and 
--dangling-ptr-deref-prob <N> 

N is 0 by default, which means no null/dangling pointer dereferences are
allowed.

-Xuejun

> -----Original Message-----
> From: csmith-dev-bounces@flux.utah.edu
> [mailto:csmith-dev-bounces@flux.utah.edu] On Behalf Of John Regehr
> Sent: Wednesday, June 08, 2011 3:20 PM
> To: csmith-dev@flux.utah.edu
> Subject: [csmith-dev] feature request: generate memory unsafe code
> 
> This is a feature request I received, and also it's something I've
> wanted myself.
> 
> The new feature is for Csmith to optionally ignore its safety analyses
> sometimes, in order to generate memory unsafety.  Obviously these
> features are turned off by default.  Probably there are three flags:
> 
> - probability of ignoring possibly-null pointer when generating a
> dereference
> 
> - probability of ignoring possibly-expired pointer when generating a
> dereference
> 
> - probability of letting an array index go OOB
> 
> The purpose of these features is to test static and dynamic memory
> safety checking tools.
> 
> John