Java Segfault with

[Tiernan Messmer]

Indeed I encountered the same issues on the non-diablo JDK as well.

In the end I found a fix somewhere (can't find it off hand) but what 
solved it for me was to edit src/lib/libz/Makefile and comment the 
following:

.if ${MACHINE_ARCH} == "amd64"
.PATH:          ${.CURDIR}/contrib/gcc_gvmat64
SRCS+=          gvmat64.S
CFLAGS+=        -DASMV -DNO_UNDERLINE
.endif

Then rebuild world (or just src/lib/libz if you're feeling lucky).

I've since moved the server in question onto an old 32bit box (the 64bit 
one was no longer available) and didn't encounter the issue again, so I 
suspect it only affects the 64bit optimised assembly version of 
longest_match.

Hope this helps.

~Tiernan Messmer


On 2011-07-29 0156, Kees Jan Koster wrote:
> Guys,
>
> I found another segfault, much like the one reported by Tiernan in http://lists.freebsd.org/pipermail/freebsd-java/2011-April/009197.html
>
> Pieter, I think this is not an issue with Diablo since I don't use that JDK. Rarther, I think this is an issue with the zip library.
>
> Any advise on how to proceed?
>
>
> This is with Java from /usr/ports/java/jdk16
>
> java version "1.6.0_03-p4"
> Java(TM) SE Runtime Environment (build 1.6.0_03-p4-kjkoster_14_jul_2011_20_52-b00)
> Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-p4-kjkoster_14_jul_2011_20_52-b00, mixed mode)
>
> #
> # An unexpected error has been detected by Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x0000000801f582a1, pid=78977, tid=0x3349400
> #
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-kjkoster_14_jul_2011_20_52-b00 mixed mode)
> # Problematic frame:
> # C  [libz.so.5+0xa2a1]  longest_match+0x1a1
> #
> # Please submit bug reports to freebsd-java at FreeBSD.org
> #
>
> More data and core file on request.
> --
> Kees Jan
>
> http://java-monitor.com/
> kjkoster at kjkoster.org
> +31651838192
>
> Change is good. Granted, it is good in retrospect, but change is good.
>