Re: [Fxruby-users] Segfaults

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

ly...@kn... a =E9crit :
> On Sun, 04 Apr 2004 10:22:47 +0200, Gilles Filippini
> <gil...@fr...> wrote :
>=20
>=20
>>It takes about 60 iterations on may box. But this problems may eventual=
y=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 :/
>=20
>=20
> Is there any possibility at all that some of this machine's memory (RAM=
) is
> going bad?

I don't think so: the fact is that it segfaults precisely at count =3D 59=
.=20
Would it be memory related I guess its behavior would be much less=20
predictible.
BTW I have other processes running (Apache, MySQL, Oracle, Mozilla,=20
aMule, distributed.net, ...) with an uptime of about one week and I=20
didn't notice anything weird.

> For what it's worth, I did go back and rebuild FXRuby-1.0.28 from the
> sources and ran the test case for several thousand iterations before fi=
nally
> killing it. So I'm fairly sure there is some other problem afoot.

I've made another test with GC disabled: no segfault (updated the=20
sourceforge bug page).
I'll try to run it tomorrow at work on another machine.
Stay tuned...

_gilles.