natObject.cc (_Jv_ObjectCheckMonitor): Use _Jv_MutexCheckMonitor instead of accessing...

	* java/lang/natObject.cc (_Jv_ObjectCheckMonitor): Use
	_Jv_MutexCheckMonitor instead of accessing mutex.owner directly.

From-SVN: r72872

diff --git a/libjava/ChangeLog b/libjava/ChangeLog
index 6c5c4d10e7bbcfcf581d68e04c131861fe0f6bfe..742e94b036cbc4e171aa0f3dba1f9548e8023f04 100644 (file)
--- a/libjava/ChangeLog
+++ b/libjava/ChangeLog
@@ -1,3 +1,8 @@
+2003-10-23  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>
+
+       * java/lang/natObject.cc (_Jv_ObjectCheckMonitor): Use
+       _Jv_MutexCheckMonitor instead of accessing mutex.owner directly.
+
 2003-10-22  Tom Tromey  <tromey@redhat.com>
 
        PR libgcj/12416:

diff --git a/libjava/java/lang/natObject.cc b/libjava/java/lang/natObject.cc
index a9f80d867f80bbc31150c019be4d879cce318e02..8618bf2c7a3a5ea98d122c89db8d32981f8550c8 100644 (file)
--- a/libjava/java/lang/natObject.cc
+++ b/libjava/java/lang/natObject.cc
@@ -1127,7 +1127,7 @@ retry:
   else
     {
       heavy_lock* hl = find_heavy(addr, he);
-      not_mine = hl ? (hl->si.mutex.owner != self) : true;
+      not_mine = hl ? _Jv_MutexCheckMonitor(&hl->si.mutex) : true;
     }
 
   release_set(&(he -> address), address);      // unlock hash entry