From owner-freebsd-current@FreeBSD.ORG  Sun Feb 29 21:49:53 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D2B8F16A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 29 Feb 2004 21:49:53 -0800 (PST)
Received: from endif.cjb.net (65-101-229-205.dnvr.qwest.net [65.101.229.205])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3391A43D1F
	for <freebsd-current@freebsd.org>;
	Sun, 29 Feb 2004 21:49:53 -0800 (PST)
	(envelope-from end@endif.cjb.net)
Received: (qmail 917 invoked from network); 1 Mar 2004 05:49:52 -0000
Received: from localhost (127.0.0.1)
  by localhost with SMTP; 1 Mar 2004 05:49:52 -0000
Date: Sun, 29 Feb 2004 22:49:52 -0700
From: Robin Schoonover <end@endif.cjb.net>
To: freebsd-current@freebsd.org
X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd5.2.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20040301054953.3391A43D1F@mx1.FreeBSD.org>
Subject: extra truss evilness
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2004 05:49:54 -0000

It's possible to panic the system with truss (doesn't appear related to
race conditions with truss).

It appears that if truss is 'watching' a process, and the process forks,
than the system could possibly hang.  However this is rare and hard to
reproduce.

However, if a process truss is 'watching' forks, and then the parent
process is interupted (^C), than the system will panic multiple times. This
has a much higher likelyhood of occuring.

I've been able to reproduce this with the following C snippet:
int pid = fork(10);
sleep(10);

Run, wait a few seconds (so we KNOW we are after fork occurs), then hit ^C.
Panic.

-- 
Robin Schoonover (aka End)
#
# "Freedom of speech in Usenet means that when you shout 'Fire!' in a
# crowded theatre, half the crowd stands up and shouts, 'Wrong theatre!'"