From: Scott Robert Ladd <coyote@coyotegulch.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Craig Thomas <craiger@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Testing: What do you want?
Date: Tue, 25 Mar 2003 09:18:06 -0500 [thread overview]
Message-ID: <3E80651E.7000606@coyotegulch.com> (raw)
In-Reply-To: <20030325001627.GC14469@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> And another thing I have found to be good at finding bugs is a sick
> mind. If you intend to crash a system and do just about anything a
> normal user wouldn't, you will stress all the code paths that are
> usually not tested.
I'll throw a couple big evolutionary simulations on one of my boxes, and
see how Linux digests it. Lovely thing about stochastic code -- you
never know what it might do. :)
I could put my wife on Linux. She's a brilliant woman of great talent --
and, alas, she is endowed with an incredible ability to wreak
unintentional destruction on technology. She has accomplished some truly
remarkable feats of software implosion -- soemtimes, without touching
the keyboard!
Let's put it this way: She got *really* angry at me once, and all of my
systems (Linboxen included) REBOOTED spontaneously in reaction to her
outburst!
Now that's what *I* call "stressing" the code!
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.
next prev parent reply other threads:[~2003-03-25 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 14:46 Testing: What do you want? Scott Robert Ladd
2003-03-24 15:39 ` Jan-Benedict Glaw
2003-03-24 17:30 ` Scott Robert Ladd
2003-03-25 0:04 ` Rob Radez
2003-03-25 17:50 ` Craig Thomas
2003-03-24 17:01 ` Alan Cox
2003-03-24 23:06 ` Craig Thomas
2003-03-25 0:16 ` Jörn Engel
2003-03-25 14:18 ` Scott Robert Ladd [this message]
2003-03-25 14:18 ` Scott Robert Ladd
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=3E80651E.7000606@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=craiger@osdl.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
/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