Re: Problem in Thread.c

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0126304000==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigEB9C58639E2FCEDA61B23423"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEB9C58639E2FCEDA61B23423
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Chris,

All object instances are in the heap.  Invoke static has no instance,
but synchronizes on the Class instance of its class.  Only the internal
VM data structures of the class are in class loader memory.

Etienne

Chris Pickett wrote:
> This is just a guess, but maybe it is because the object instance for an
> INVOKESTATIC is not on the heap but in class loader memory.

-- 
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

--------------enigEB9C58639E2FCEDA61B23423
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEQsnPjyrJi4rH84gRAvqtAJ4ghJhZsehKY8s7bXttqpPBb046LQCfQIgN
Sa2LuziDx4S0dm7hEvGB2vU=
=opl4
-----END PGP SIGNATURE-----

--------------enigEB9C58639E2FCEDA61B23423--


--===============0126304000==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SableVM-devel mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-devel

--===============0126304000==--