From owner-freebsd-current@FreeBSD.ORG  Mon May 14 07:50:21 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 45E3A16A406;
	Mon, 14 May 2007 07:50:21 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.208.78.105])
	by mx1.freebsd.org (Postfix) with ESMTP id 2601513C44B;
	Mon, 14 May 2007 07:50:21 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
	[127.0.0.1])
	by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id
	l4E7kUPs002862; Mon, 14 May 2007 00:46:30 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id
	l4E7kU1r002861; Mon, 14 May 2007 00:46:30 -0700 (PDT)
	(envelope-from sgk)
Date: Mon, 14 May 2007 00:46:30 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Dag-Erling Sm??rgrav <des@des.no>
Message-ID: <20070514074630.GA2818@troutmask.apl.washington.edu>
References: <864pmg1t1s.fsf@dwp.des.no>
	<20070513183009.GA96018@troutmask.apl.washington.edu>
	<86646wzfv0.fsf@dwp.des.no>
	<20070513192836.GA94258@troutmask.apl.washington.edu>
	<46478626.9060301@FreeBSD.org>
	<20070513230055.1dbd22f5.rnsanchez@wait4.org>
	<20070514020635.GA99892@troutmask.apl.washington.edu>
	<20070514022620.GA52887@nagual.pp.ru>
	<20070514024316.GA197@troutmask.apl.washington.edu>
	<86ps53x3ci.fsf@dwp.des.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86ps53x3ci.fsf@dwp.des.no>
User-Agent: Mutt/1.4.2.2i
Cc: Ricardo Nabinger Sanchez <rnsanchez@wait4.org>, freebsd-current@freebsd.org
Subject: Re: Process for requesting reverting patch?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 14 May 2007 07:50:21 -0000

On Mon, May 14, 2007 at 09:37:49AM +0200, Dag-Erling Sm??rgrav wrote:
> Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
> > Read the entire thread.  tcsh hangs when invoked from gdb with a
> > .cshrc that contains
> 
> "tcsh hangs when invoked from gdb"?
> 
> gdb uses ptrace(2), which breaks the process hierarchy - the debugged
> process is reparented to gdb.  When the debugged process forks and gdb
> attaches to the child, the child will seem - from the parent's
> perspective - to disappear into thin air.
> 
> This has never worked correctly in FreeBSD and is completely unrelated
> to tcsh, so you can get off mp@'s back already.
> 
> Fixing it is hard.  I've tried.  It seems easy until you realize that
> you need to rewrite most of kern_wait().
> 

des, get off your high horse!

gdb has always worked for me until the recent import of tcsh.

I've use the freebsd base system gdb(1) for nearly 15 years
without problems.  The recent tcsh import has broken gdb.  If you
can fix it, fine; otherwise, crawl back under your rock.

-- 
Steve