Date: Mon, 26 Jan 2004 18:29:13 +0200 From: Panagiotis Astithas <past@noc.ntua.gr> To: gwk@rahn-koltermann.de Cc: freebsd-java@freebsd.org Subject: Re: JDWP error with libthr (-p6) Message-ID: <40154059.5040804@noc.ntua.gr> In-Reply-To: <27942123$1075128485401528a561a694.54838164@config12.schlund.de> References: <27942123$1075128485401528a561a694.54838164@config12.schlund.de>
next in thread | previous in thread | raw e-mail | index | archive | help
gwk@rahn-koltermann.de wrote: > Hi, > > whenever I try to use Java (JPDA) debugging with jdk14-p6 with libthr, I > get: > > FATAL ERROR in native method: JDWP "util.c" (Jan 24 2004), line 1194: > Unexpected error, error code = 51 (JVMDI_ERROR_NOT_MONITOR_OWNER) > > I think this has been reported before and was attributed to gdb being > incompatible with libthr, but I am most sure gdb is out of the loop > here. > Note I am not debugging the JVM (with gdb), I'm debugging a Java > application using another Java application (Eclipse) as the debugger. > > The problem is easy to reproduce. Just take your favorite hello-world > java program, set a breakpoint on some line, and start the (Eclipse) > debugger on it. You will get the above error if you run with libthr but > > all will be well if you run with libc_r. 1.4.2p5 was linked against libc_r, 1.4.2p6 was linked against libkse. Are you sure you are not mixing threading subsystems? Do you use a global mapping from libc_r and/or libkse to libthr? -- Panagiotis Astithas Electrical & Computer Engineer, PhD Network Management Center National Technical University of Athens, Greece
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40154059.5040804>