From owner-freebsd-java@FreeBSD.ORG Mon May 10 09:46:26 2010 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59C79106564A for ; Mon, 10 May 2010 09:46:26 +0000 (UTC) (envelope-from achill@matrix.gatewaynet.com) Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211]) by mx1.freebsd.org (Postfix) with ESMTP id A73C18FC1D for ; Mon, 10 May 2010 09:46:24 +0000 (UTC) Received: from smadev.internal.net (localhost.internal.net [127.0.0.1]) by smadev.internal.net (8.14.2/8.14.2) with ESMTP id o4A9kMGX072894 for ; Mon, 10 May 2010 12:46:22 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Received: from localhost (localhost [[UNIX: localhost]]) by smadev.internal.net (8.14.2/8.14.2/Submit) id o4A9kM2o072893 for freebsd-java@freebsd.org; Mon, 10 May 2010 12:46:22 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: freebsd-java@freebsd.org Date: Mon, 10 May 2010 12:46:21 +0300 User-Agent: KMail/1.9.7 References: <4BE11114.5030306@gmail.com> <201005070902.22700.achill@matrix.gatewaynet.com> <4BE4843E.6030901@gmail.com> In-Reply-To: <4BE4843E.6030901@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <201005101246.22215.achill@matrix.gatewaynet.com> Subject: Re: openjdk6 crashes X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2010 09:46:26 -0000 =D3=F4=E9=F2 Saturday 08 May 2010 00:21:02 =EF/=E7 Peter Palmreuther =DD=E3= =F1=E1=F8=E5: >=20 > *erm* Maybe. For fixed conditions (which are seldom in my experience). Mo= st > times I've seen systems crashing here and there with no fixed script or > program if hardware dies. Simply because it's not deterministic what > temperature the system will have and what program will be at which memory > address. The only fixed crashing point can be the hard disk, which I thin= k I > can exclude due to the recompilation and therefore "relocation" on disk (= i.e. > different inodes being used). it has happened to me with my home FreeBSD box, crashing every morning at 0= 3:00, after a system upgrade (i think it was from 6.2->7.1). The easy answer was to accuse the software (upgrade), however what was most= probably happening was that the system upgrade made a previously hidden hardware problem to ap= pear. The system did not came back to stability, untill i replaced the motherboar= d. (after having tried changing the usual suspect RAM) The program causing the panic was periodic daily. =46or some reason, the same script on the same hardware with the previous 6= =2E2 kernel was working ok. >=20 > And to come to an end: if I see a program written in C++ (like OpenJDK/JV= M) > constantly fails on an assertion (like in my case: 'Error: assert(sp() >= =3D > inputs,"must have enough JVMS stack to execute")') I expect the assertion= to > not match first and think about corrupt memory a few hundred positions la= ter > on the "check list". That's at least what assertions are for: make the pr= ogram > fail if something is recognizable wrong. If every "assert fail" would be a > memory defect unless 100% proven not to be that would render assertions > useless, wouldn't it? >=20 > But thanks for your help and input; Maybe somebody else has any idea abou= t why > "sp()" is less than "input" when compiling (hotspot compiling?) this spec= ial > class in OpenJDK?!? Anyway Have your tried=20 =2D native jdk=20 =2D the binary diablo=20 =2D the linux jdk with linuxolator ?? =2D-=20 Achilleas Mantzios