From owner-freebsd-bugs@FreeBSD.ORG Sun May 25 14:25:12 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A1481065670; Sun, 25 May 2008 14:25:12 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 75C168FC12; Sun, 25 May 2008 14:25:11 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <483976C6.8010805@FreeBSD.org> Date: Sun, 25 May 2008 16:25:10 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Jille References: <200805251306.m4PD6PpX035467@freefall.freebsd.org> <483971D4.5080907@FreeBSD.org> <483973E1.5010507@quis.cx> In-Reply-To: <483973E1.5010507@quis.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org, ache@FreeBSD.org Subject: Re: bin/123977: Segmentation fault in dialog with ghostscript-gpl-nox11 port X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 May 2008 14:25:12 -0000 Jille wrote: > Kris Kennaway schreef: >> ache@FreeBSD.org wrote: >>> Synopsis: Segmentation fault in dialog with ghostscript-gpl-nox11 port >>> >>> State-Changed-From-To: open->patched >>> State-Changed-By: ache >>> State-Changed-When: Sun May 25 13:05:41 UTC 2008 >>> State-Changed-Why: MAX_LEN bumped to 4096 long time ago >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=123977 >>> _______________________________________________ >>> freebsd-bugs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs >>> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" >>> >>> >> >> Are you certain this is relevant here? > Confirmed. > > My 6.2 box had 2048, my 6.3 had 4096. > Changing it to 4096 on my 6.2, recompiling, fixed it. > Changing it back to 2048, recompiling, rebroke it. > > So this is really the issue. OK, thanks for confirming. I think we can close this PR now as a duplicate of the older one. You are correct that 4096 is just a bandaid, but short of hard work to fix the many deficiencies in dialog this is the best available solution. Kris