From: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] portablility of random.mli in the stdlib
Date: Sat, 30 Apr 2011 14:06:34 +0200 [thread overview]
Message-ID: <BANLkTina=xhUAXb+N3f0EnNEhEigf9oBiA@mail.gmail.com> (raw)
In-Reply-To: <4DBBF1D8.6020105@gmail.com>
2011/4/30 Török Edwin <edwintorok@gmail.com>:
> On 04/30/2011 02:14 PM, Christophe Raffalli wrote:
>
> Why should a random generator give the same results over multiple
> versions and architectures?
> Starting from same seed is useful only for debugging.
I wrote a fuzzer once: the principle is to generate random entries for
a program, and see if it crashes. When it does, instead of printing
the entry in the log file, you just remember the seed that produced
the entry. With that, you are able to reproduce the crash easily
Cheers
Alexandre Pilkiewicz
next prev parent reply other threads:[~2011-04-30 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 10:37 Christophe Raffalli
2011-04-30 11:14 ` Christophe Raffalli
2011-04-30 11:26 ` Török Edwin
2011-04-30 11:42 ` Christophe Raffalli
2011-04-30 15:38 ` Andrei Formiga
2011-04-30 12:06 ` Alexandre Pilkiewicz [this message]
2011-04-30 13:33 ` Andrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTina=xhUAXb+N3f0EnNEhEigf9oBiA@mail.gmail.com' \
--to=alexandre.pilkiewicz@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=edwintorok@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox