From owner-freebsd-questions@FreeBSD.ORG Mon Apr 13 16:21:06 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F7FC906; Mon, 13 Apr 2015 16:21:06 +0000 (UTC) Received: from sdf.org (ma.sdf.org [192.94.73.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ma.sdf.org", Issuer "ma.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 002C3146; Mon, 13 Apr 2015 16:21:05 +0000 (UTC) Received: from ma.sdf.org (IDENT:U2FsdGVkX18lRdqUywr0YVdldyK1JZhzOeV8WmlifDM@ma.sdf.org [192.94.73.31]) by sdf.org (8.14.4/8.14.3) with ESMTP id t3DGKwQ7024558; Mon, 13 Apr 2015 16:20:58 GMT MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 13 Apr 2015 11:20:58 -0500 From: cpet To: Tim Gustafson Subject: Re: Vim/Vi/Bash Segfaults After Upgrade to 10.1 In-Reply-To: References: Message-ID: X-Sender: cpet@sdf.org User-Agent: Roundcube Webmail/1.0.1 Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 16:21:06 -0000 On 2015-04-13 11:11, Tim Gustafson wrote: > After upgrading a 10.0 box to 10.1-RELEASE-p9, I am getting really odd > segfaults when running vi, vim or bash. So far, no other programs I've > found are segfaulting since the upgrade. > > I've re-built and installed world, followed by a "make delete-old > delete-old-libs", followed by a "portmaster -fad" three times, to no > avail. > > A truss of a vim process is attached. It looks like it's segfaulting > after a call to sigprocmask(). > > Bash is behaving very strangely. It seems to segfault when logging in > as a user who has bash set as their shell, but not when you run bash > from within tcsh. Put another way, as root, if I "su bashuser", the > system hangs for a few seconds and then segfaults. If I just run > "bash" as root, it works without a hitch. Just to make things more > interesting, if I "truss -f su bashuser", it does not segfault. > Running "su bashuser truss -o /tmp/bash.txt bash" causes the hang and > eventual segfault, but never creates /tmp/bash.txt > > I am totally at a loss. Has anyone else seen this behavior? Any > ideas as to what may be going on? > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" You can do it 100 times and it will give you the same outcome, normally when this happens you remove all ports and build the ones you want, this helps in old libs being compiled, Also people do strange things in hopes to make things faster an increase of 0.000000001% when adding CPUFLAGS= bleh isn't really much to award for and causes issues in the long run. Mixing PKGng and Ports causes issues as well. Personally I don't run bash as I classify it as a linuxism, but whenever I upgrade I remove all my ports and recompile, not using portmaster as it has been known to cause problems. My 2 cents