From owner-freebsd-java@FreeBSD.ORG Wed Jul 12 14:14:42 2006 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 006B816A4DA for ; Wed, 12 Jul 2006 14:14:41 +0000 (UTC) (envelope-from lists@intricatesoftware.com) Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.4.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B0A443D6A for ; Wed, 12 Jul 2006 14:14:37 +0000 (GMT) (envelope-from lists@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta4.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0J2A00752NKFNZ11@mta4.srv.hcvlny.cv.net> for freebsd-java@freebsd.org; Wed, 12 Jul 2006 10:14:40 -0400 (EDT) Date: Wed, 12 Jul 2006 10:14:35 -0400 From: Kurt Miller In-reply-to: <200607111613.26814@centrum.cz> To: freebsd-java@freebsd.org Message-id: <200607121014.35525.lists@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-6 Content-transfer-encoding: quoted-printable Content-disposition: inline References: <200607111613.26814@centrum.cz> User-Agent: KMail/1.9.3 Subject: Re: diablo 1.5 crash X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kurt@intricatesoftware.com List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 14:14:42 -0000 On Tuesday 11 July 2006 10:13 am, Jan Zach wrote: > # An unexpected error has been detected by HotSpot Virtual Machine: > # > #=A0 SIGSEGV (0xb) at pc=3D0x43657d18, pid=3D4258, tid=3D0x863fa00 > # > # Java VM: Java HotSpot(TM) Client VM (diablo-1.5.0_07-b00 mixed mode) > # Problematic frame: > # C=A0 [libfontmanager.so+0x62d18]=A0 ExtractPureT1FromPCType1+0xb38 This is on line j2se/src/share/native/sun/font/t2k/t1.c:2046 in the port version of the jdk. Nothing obvious immediately jumps out at me. It could be caused by a bad Type1 font. Is it reproduceable? If so, perhaps you could determine which Type1 font is causing it. =2DKurt