native jdk release schedule question

[Nick Johnson]

FWIW, it looks like the trouble comes from
hotspot/src/share/vm/prims/jvmdi.cpp because monitor->monitor().raw_notify
(or raw_wait or raw_notifyAll or raw_exit) is returning
ObjectMonitor::OM_ILLEGAL_MONITOR_STATE.

That seems to be triggered from
hotspot/src/os/bsd/vm/objectMonitor_bsd.cpp like this:

 int ObjectMonitor::raw_notify(TRAPS) {
   if (THREAD != _owner) {
     return OM_ILLEGAL_MONITOR_STATE;
   }

So at first glance it looks like a thread ownership problem.  Don't have
time to dig any deeper ATM.

   Nick

On Fri, 30 Jul 2004, Panagiotis Astithas wrote:

> Nick Johnson wrote:
> > On Mon, 26 Jul 2004, Panagiotis Astithas wrote:
> >
> >
> >>The jdk works fine with KSE as long as you don't use debugging. Have you
> >>tried using jdb yet?
> >
> >
> > Just curious: how does the problem with jdb manifest itself?
>
> You get messages like this:
>
> % jdb BuggyWindow2
> Initializing jdb ...
>  > run
> run BuggyWindow2
> VM start exception: VM initialization failed for:
> /usr/local/jdk1.4.2/jre/bin/java -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=edgar.ebs.gr:60765,suspend=y
> BuggyWindow2
>
> FATAL ERROR in native method: JDWP "util.c" (Mar 15 2004), line 1194:
> Unexpected error, error code = 51 (JVMDI_ERROR_NOT_MONITOR_OWNER)
>
>
> Fatal error:
> Target VM failed to initialize.
>
>
>
> Cheers,
> --
> Panagiotis Astithas, PhD
> R&D Manager
> EBS, Electronic Business Systems Ltd.
> 18 Evgenidou Street, 115 25, Athens GREECE
> Phone: +30 210 674 7631
> Fax: +30 210 674 7601
> http://www.ebs.gr
>

-- 
"The aptly-named morons.org is an obscenity-laced screed..."
	-- Robert P. Lockwood, Catholic League director of research
Nick Johnson, version 2.1                             http://web.morons.org/