www.delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin-developers AT sources DOT redhat DOT com |
From: | Matt <matt AT use DOT net> |
X-Sender: | matt AT cesium DOT clock DOT org |
To: | cygwin-developers AT sources DOT redhat DOT com |
Subject: | crashme testing |
Message-ID: | <Pine.NEB.4.10.10010291235390.20792-100000@cesium.clock.org> |
MIME-Version: | 1.0 |
Date: | Sun, 29 Oct 2000 12:46:28 -0800 |
http://people.delphi.com/gjc/crashme.html I've done some testing of the 'crashme' program against some of the new cygwin snapshots and have gotten interesting results (high CPU usage, lockups, etc). I've tried to articulate things via strace, but don't really know what to look for. The strace logs are pretty huge :/ If anyone wants to give it a try, the supplied makefile with crashme works with cygwin. The commandline I've been trying is: 'crashme +2000 31337 100'. Hope this helps find some bugs, sorry I couldn't give more detail..
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |