Re: [Fxruby-users] Segfaults

[Gilles F. <gil...@fr...>]

Lyle Johnson a =E9crit :
>=20
> On Apr 2, 2004, at 4:23 PM, Gilles Filippini wrote:
>=20
>> It's been long time since I've tried FXRuby intensively :o)
>> I'm back with the same kind of segfaults I had then.
>=20
>=20
> OK.
>=20
>> For example FXEvent appears corrupted after a while in an onPaint=20
>> callback. I don't have a simple test case yet. I'll try to narrow the=20
>> probelm using valgrind. The bug vanishes when GC is disabled.
>=20
>=20
> Yes, if you can send me a simple test case for this one, please do.
>=20
>> Just to try, I've launched an old test case (not related to the above=20
>> bug) I used when there were problems with TreeList items. Segfault aga=
in.
>=20
>=20
> Yes, I still have this test case and run it before each release ;) It i=
s=20
> the "stress1.rb" case, under the FXRuby tests directory.
>=20
> How many iterations did it take for this one to crash on your machine? =
I=20
> ask because I'm running it right now (with my development version of=20
> FXRuby) and so far it's gotten to "count=3D1800" without crashing. I wi=
ll=20
> go back and build FXRuby-1.0.28 from the earlier sources, but I'm fairl=
y=20
> sure I ran this test before releasing that version too.
>=20

It takes about 60 iterations on may box. But this problems may eventualy=20
be unrelated to FXRuby:

- the segfault occurs without any Ruby msg. It's a brutal segfault:
...
count =3D 58
count =3D 59
Erreur de segmentation
maison:~/devel/bug$

- I've run the very same test case using valgrind and it's gone as far=20
as 6000+ before I stop it.

Well... I don't know where to look now :/

_gilles.