From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 15:17:30 2003 Return-Path: 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 EF77137B404 for ; Thu, 17 Jul 2003 15:17:30 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2BDA43F3F for ; Thu, 17 Jul 2003 15:17:27 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h6HMHPju055633; Thu, 17 Jul 2003 15:17:26 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h6HMHPOF055632; Thu, 17 Jul 2003 15:17:25 -0700 (PDT) Date: Thu, 17 Jul 2003 15:17:25 -0700 From: "David O'Brien" To: Kenneth Culver Message-ID: <20030717221725.GA55448@dragon.nuxi.com> References: <20030717160215.G67028@alpha.yumyumyum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030717160215.G67028@alpha.yumyumyum.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.1-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: problem after gcc import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 22:17:31 -0000 On Thu, Jul 17, 2003 at 04:12:24PM -0400, Kenneth Culver wrote: > I use gvim as my editor-of-choice for programming in C, and now this > happens: > kaoru:~:> gvim > Vim: Caught deadly signal BUS > Vim: Finished. ... > Any ideas? Read freebsd-current. :-) A suggestion was given this week: Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) Date: Wed, 16 Jul 2003 23:14:30 -0700 To: "Karel J. Bosschaart" On Tue, Jul 15, 2003 at 11:07:40AM +0200, Karel J. Bosschaart wrote: > FWIW, the new behaviour of vim is caused by patch 6.2.015. I added > 015 to BADPATCHES in the ports Makefile and reinstalled. gvim works > as usual now.