From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 05:15:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84E1216A420 for ; Fri, 28 Sep 2007 05:15:11 +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 612CF13C469 for ; Fri, 28 Sep 2007 05:15:11 +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.14.1) with ESMTP id l8S5CqfC034653; Thu, 27 Sep 2007 22:12:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.14.1/Submit) id l8S5Cq0l034652; Thu, 27 Sep 2007 22:12:52 -0700 (PDT) (envelope-from sgk) Date: Thu, 27 Sep 2007 22:12:52 -0700 From: Steve Kargl To: Eric Schuele Message-ID: <20070928051252.GA34607@troutmask.apl.washington.edu> References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> <46FC89FB.2070506@computer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FC89FB.2070506@computer.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... 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: Fri, 28 Sep 2007 05:15:11 -0000 On Thu, Sep 27, 2007 at 11:58:35PM -0500, Eric Schuele wrote: > On 09/27/2007 23:29, Steve Kargl wrote: > > On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: > >> Has anyone seen behavior like this? What else can I provide that might > >> help diagnose this? > >> > > > > Are you by any chance using tcsh as your shell? > > > > heh... Yes, as a matter of fact. How is that affecting me? I've always > used tcsh and not had these troubles. > Signal handling in tcsh is broken, and one manifestation of the problem is the behavior you're seeing with gdb. I've repeatedly asked to have the 6.15.0 version of tcsh backed out of src/ to the previously working 6.14.0 version, but no one who can affect such a change seems to think a default user shell with broken signal handling is a problem. The only workaround that I've found is "setenv SHELL sh" prior to executing gdb. -- Steve