From owner-freebsd-bugs@FreeBSD.ORG  Mon Jun  2 07:36:24 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6687937B401; Mon,  2 Jun 2003 07:36:24 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0296643FB1; Mon,  2 Jun 2003 07:36:24 -0700 (PDT)
	(envelope-from dwmalone@FreeBSD.org)
Received: from freefall.freebsd.org (dwmalone@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h52EaNUp060306;
	Mon, 2 Jun 2003 07:36:23 -0700 (PDT)
	(envelope-from dwmalone@freefall.freebsd.org)
Received: (from dwmalone@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h52EaNvn060302;
	Mon, 2 Jun 2003 07:36:23 -0700 (PDT)
Date: Mon, 2 Jun 2003 07:36:23 -0700 (PDT)
From: David Malone <dwmalone@FreeBSD.org>
Message-Id: <200306021436.h52EaNvn060302@freefall.freebsd.org>
To: marka@isc.org, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: bin/52746: tcsh fails to handle large arguements
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2003 14:36:24 -0000

Synopsis: tcsh fails to handle large arguements

State-Changed-From-To: open->feedback
State-Changed-By: dwmalone
State-Changed-When: Mon Jun 2 07:31:17 PDT 2003
State-Changed-Why: 
Mark,

I'd run into this problem a few years ago, but never had a chance
to get to the bottom of it.  From running ktrace, it looks like
this problem is related to vfork.  For me, running tcsh with the
-F flag (ie., use fork not vfork) seems to work around the problem.

I'm guessing what is happening is that something is handling the
arg too long error and clobbering the vforked stack.  I'll try to
do a bit more digging, but you might like to check if-F helps in
your case too...

	David.

http://www.freebsd.org/cgi/query-pr.cgi?pr=52746