Eclipse-2.3.1 and 5.2-CURRENT woes

[Panagiotis Astithas]

On Tuesday 13 April 2004 07:20, Doug Poland wrote:
> I guess I'm not cut out for the bleeding edge :(   I recently updated
> my 5.2.1-RELEASE box to -CURRENT.  Many ports were "broken" and I
> eventually ran a portupgrade -af.  That fixed most everything except
> Eclipse.
>
> Now I cannot run any type of debug session.  Normal "run" works but
> not debug.  This is what I get....
>
> "Exception occurred during launch   Reason: Cannot connect to VM"
>
> FATAL ERROR in native method: JDWP "util.c" (Apr  9 2004), line 1194:
> Unexpected error, error code = 51 (JVMDI_ERROR_NOT_MONITOR_OWNER)
>
> I've seen some references to libthr and libc_r during my googling but
> must admit I don't understand the implications thereof.
>
> Thanks for your help.
>
>
> % uname -a
> FreeBSD jericho.polands.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon
> Apr  5 22:57:43 CDT 2004
> djp at jericho.polands.org:/usr/obj/usr/src/sys/JERICHO  i386
>
> % pkg_info | egrep -i 'eclipse|jdk'
> eclipse-2.1.3_1     An open extensible IDE for anything and nothing in
> particul jdk-1.4.2p6_4       Java Development Kit 1.4.2

Try to use /etc/libmap.conf to map libpthread/libkse/libthr to libc_r.

Cheers,
-- 
Panagiotis Astithas
Electrical & Computer Engineer, PhD
Network Management Center
National Technical University of Athens, Greece

-- 
Panagiotis Astithas
Electrical & Computer Engineer, PhD
Network Management Center
National Technical University of Athens, Greece