From owner-freebsd-ports Sun Nov 5 16:59:45 2000 Delivered-To: freebsd-ports@freebsd.org Received: from area51.slashnet.org (area51.slashnet.org [208.222.214.95]) by hub.freebsd.org (Postfix) with ESMTP id 3067937B4CF; Sun, 5 Nov 2000 16:59:43 -0800 (PST) Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.107.69]) by area51.slashnet.org (Postfix) with ESMTP id 18C8B14D436; Sun, 5 Nov 2000 19:59:29 -0500 (EST) Received: by edgemaster.zombie.org (Postfix, from userid 1001) id 662B798F2; Sun, 5 Nov 2000 18:59:21 -0600 (CST) Date: Sun, 5 Nov 2000 18:59:21 -0600 From: Sean Kelly To: ache@FreeBSD.org Cc: gsutter@zer0.org, freebsd-ports@freebsd.org Subject: Re: ports/22444: screen segfault Message-ID: <20001105185921.A57472@edgemaster.zombie.org> References: <20001031182149.AF25798A4@edgemaster.zombie.org> <20001031140837.B8380@klapaucius.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001031140837.B8380@klapaucius.zer0.org>; from gsutter@zer0.org on Tue, Oct 31, 2000 at 02:08:37PM -0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 31, 2000 at 02:08:37PM -0800, Gregory Sutter wrote: > On 2000-10-31 12:21 -0600, smkelly@zombie.org wrote: > > > > >Number: 22444 > > >Category: ports > > >Synopsis: The 'screen' port has reproducable segfaults > > > > screen-3.9.8_3 > > > > FreeBSD edgemaster.zombie.org 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Tue Oct 24 0 > > 0:37:00 CDT 2000 smkelly@edgemaster.zombie.org:/usr/obj/usr/src/sys/EDGEMAST > > ER i386 > > > > >Description: > > > > Under reproducable (though not well understood) and some unknonw conditions > > screen will crash with signal 11. > > > > >How-To-Repeat: > > > > If I start the mutt MUA from within screen, screen will always segfault when > > I open my mail folders. I assume it has something to do with the appearance > > of my screen at the time, but I am not sure. I have also seen screen crash > > due to the EPIC IRC client. The actual condition it crashes under is unknown > > to me. > > I have reason to believe that this is a problem with screen and the > new ncurses that was imported to -STABLE. However, since none of my > computers have a -STABLE from after the ncurses import, I cannot test > my assertion. I would consider 'screen' to be one of the most basic applications of my working environment. Having it be broken is very difficult to work around. Is there any plan to fix the port or ncruses, or am I going to be forced to build a static screen on an older FreeBSD system? -- Sean Kelly or PGP KeyID: 4AC781C7 http://www.sean-kelly.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message