From owner-freebsd-current@FreeBSD.ORG Mon May 14 03:56:53 2007 Return-Path: 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 BAC3B16A400 for ; Mon, 14 May 2007 03:56:53 +0000 (UTC) (envelope-from mp@FreeBSD.org) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id 574CE13C448 for ; Mon, 14 May 2007 03:56:53 +0000 (UTC) (envelope-from mp@FreeBSD.org) Received: (qmail 17526 invoked by uid 0); 14 May 2007 03:56:52 -0000 Received: from 24.4.239.7 (HELO mp.peek.org) (24.4.239.7) by relay03.pair.com with SMTP; 14 May 2007 03:56:52 -0000 X-pair-Authenticated: 24.4.239.7 Message-ID: <4647DDF5.6070400@FreeBSD.org> Date: Sun, 13 May 2007 20:56:37 -0700 From: Mark Peek User-Agent: Thunderbird 2.0.0.0pre (Macintosh/20070419) MIME-Version: 1.0 CC: freebsd-current@freebsd.org 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> <20070513225255.GA96773@troutmask.apl.washington.edu> <20070513230634.GA96931@troutmask.apl.washington.edu> <6eb82e0705131931j4274046ew588ba5f28c0930e2@mail.gmail.com> <20070514025129.GB197@troutmask.apl.washington.edu> <6eb82e0705132011r6bad8de6qb38eb6e6bcb4beb0@mail.gmail.com> <20070514031852.GA634@troutmask.apl.washington.edu> In-Reply-To: <20070514031852.GA634@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2007 03:56:53 -0000 On 5/13/07 8:18 PM, Steve Kargl wrote: > For any one that thinks I'm some kind of idiot. I've > used the base system gdb for the past 3 years to debug > gcc. It worked flawlessly until the recent tcsh import. I was able to reproduce a gdb hang after receiving the additional information about the "setenv MAIL /var/log/`whoami`" in the .cshrc file. I believe it might be due to some changes in signal handling between tcsh 6.14 and 6.15. I'll try debugging it further myself and I also notified the tcsh bug list about this issue in case someone on that list can help as well. Mark