From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 23 22:20:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8221E6D0 for ; Sun, 23 Feb 2014 22:20:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C21E1B8D for ; Sun, 23 Feb 2014 22:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1NMK1m7055347 for ; Sun, 23 Feb 2014 22:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1NMK1CK055346; Sun, 23 Feb 2014 22:20:01 GMT (envelope-from gnats) Date: Sun, 23 Feb 2014 22:20:01 GMT Message-Id: <201402232220.s1NMK1CK055346@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Philippe Michel Subject: Re: kern/185964: Codeset conversion to Chinese Simplified (HZ) is broken / segfaults X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Philippe Michel List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 22:20:01 -0000 The following reply was made to PR kern/185964; it has been noted by GNATS. From: Philippe Michel To: bug-followup@FreeBSD.org, manuel-freebsd@mausz.at Cc: fluffy@FreeBSD.org Subject: Re: kern/185964: Codeset conversion to Chinese Simplified (HZ) is broken / segfaults Date: Sun, 23 Feb 2014 23:08:37 +0100 (CET) This bug does not seem to affect only explicit conversion to Chinese. At least it breaks the deskutils/fbreader port (it coredumps at startup with the deeper frames identical to those mentionned in the bug report). The patches attached to the first followup fix this as well. Could you consider increasing its priority ? Best regards, Philippe Michel