Re: Problem in Thread.c

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

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

Hi Sebastien,

I definitely think that the framework outlined in

 http://sablevm.org/lists/sablevm-devel/2006-April/000672.html

is needed.  It will be useful now and later, for developing, debugging,
testing and maintaining any complex GC algorithm we include in SableVM.

Etienne

S=E9bastien Adam wrote:
> I allocated the larger objects in the oldest generation. I think this i=
s
> the source of the problem. Since I allocate these objects in the
> nursery, everything works perfectly... and for all heap size...

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


--------------enigBB2EDFDC424A41C584B7FF1F
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

iD8DBQFEQ58njyrJi4rH84gRAjJmAJ4iyy1pifKF+tI40bulRB0ZXLx/OACcCziu
CQwQlMc7wb8LNnfa7BxKl9M=
=DS4C
-----END PGP SIGNATURE-----

--------------enigBB2EDFDC424A41C584B7FF1F--


--===============1834098580==
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

--===============1834098580==--