Re: Java binaries from this summer loops on current

[Andrew Doran <ad%netbsd.org@localhost>]

On Thu, Dec 04, 2008 at 12:54:11PM -0700, Sverre Froyen wrote:

> I've run into what appears to be a lack of backwards compatibility in i386 
> NetBSD current.
...
> Since I have native Java working, I'm not sure if this is worth investigating 
> further.  On the other hand, since it may indicate a backwards compatibility 
> issue, I thought I should report it.
...
> #1  0xbbbe282d in pthread_mutex_trylock () from /usr/lib/libpthread.so.0
> #2  0x00000002 in ?? ()                                                 
> #3  0xbb4de534 in ?? ()                                                 
>    from /usr/pkg/java/jdk-1.6.0-/jre/lib/i386/client/libjvm.so          
> #4  0xbbbe26c9 in pthread_mutex_trylock () from /usr/lib/libpthread.so.0
> #5  0xbb3a0594 in Mutex::lock_without_safepoint_check ()                
>    from /usr/pkg/java/jdk-1.6.0-/jre/lib/i386/client/libjvm.so          
> #6  0xbb3b66da in java_start ()                                         
>    from /usr/pkg/java/jdk-1.6.0-/jre/lib/i386/client/libjvm.so          
> #7  0xbbbe5afb in pthread_create () from /usr/lib/libpthread.so.0       
> #8  0xbbb32480 in swapcontext () from /usr/lib/libc.so.12               

Between 4.0 and 5.0 the layout of pthread_mutex_t was changed in -current,
twice.

The second change was made to restore ABI compatibility between 4.0 and 5.0.
If you compiled a libary/app that uses libpthread on an earlier -current,
you need to recompile it again with 4.0, or 5.0, or -current from now for
it to be compatible with all three.

Andrew