[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [csmith-dev] feature request: generate memory unsafe code
Is there something I have to do to enable this option?
$ csmith --null-ptr-deref-prob 50 # side question: is <N> a
percentage? should i use 0.5 or 50 for 50%?
invalid option --null-ptr-deref-prob at: 1
I `git clone`ed the most recent version from
I think this is my current local version, although I am not a git user
so I'm not really sure (I found the command on the web):
$ git rev-parse HEAD
After I checked it out, I just `./configured`, `make`ed, and `make install`ed.
On Sat, Jun 18, 2011 at 11:47 AM, Xuejun Yang <firstname.lastname@example.org> wrote:
> 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
> --null-ptr-deref-prob <N> and
> --dangling-ptr-deref-prob <N>
> N is 0 by default, which means no null/dangling pointer dereferences are
>> -----Original Message-----
>> From: email@example.com
>> [mailto:firstname.lastname@example.org] On Behalf Of John Regehr
>> Sent: Wednesday, June 08, 2011 3:20 PM
>> To: email@example.com
>> 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
>> - probability of ignoring possibly-expired pointer when generating a
>> - probability of letting an array index go OOB
>> The purpose of these features is to test static and dynamic memory
>> safety checking tools.