Re: Problem in Thread.c

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

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

Hi Sebastien,

Can you reproduce this problem in a plain version of SableVM 1.13 (i.e.
without your new GC stuff)?  If yes, can you submit a bug report at
http://sablevm.org/bugs.html with the instructions (and any required
code example) to reproduce the problem?

If not, then you should probably create a "personal tag"[*] by copying
the version of your sandbox that exhibits the problem, and send us
another message with the instructions to reproduce the problem.

[*] e.g.
$ export $SVN=3Dsvn+ssh://svn.sablevm.org/public/developers/sadam
$ svn cp [-r????]\
  $SVN/sandbox/[???] $SVN/tags/lock_gc_bug

This will create the following tag for others to see:

 svn://svn.sablevm.org/developers/sadam/tags/lock_gc_bug

The idea is that you can then continue changing your sandbox without
worrying, as others will fetch the "frozen snapshot" of your sandbox
represented by the tag.

Hints for finding the problem:  You could scan the heap, at the start of
every GC, before copying any object, and verify that all lockwords do
have their least significant bit set.  You should also scan the heap at
the end of GC, and do the same check.  This would reveal whether the
problem is in GC or elsewhere.

Have fun!

Etienne

S=E9bastien Adam wrote:
> I developed a new generational gc in SableVM release 1.13.
>=20
> I get a segmentation fault at the last instruction in the following
> code. This instruction is found at line 1364 in the method
> _svmf_enter_object_monitor of Thread.c.
>...=20
> I don't work a lot with the Thread code but I don't think the problem i=
s
> in _svmf_enter_object_monitor. Is there somebody that can help me to
> resolve this problem? Where should I look?

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


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

iD8DBQFEQmJijyrJi4rH84gRAulsAJ9ntn8c6M2joCmV96nwWmNoSDmq9gCfY1N3
XmhGxwa30Un+mA7/skMuYWM=
=lXgv
-----END PGP SIGNATURE-----

--------------enig3991BD17BD0DB67D72122AB0--


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

--===============0478569069==--