Re: [Fxruby-users] Segfaults

[jeroen <je...@fo...>]

On Monday 05 April 2004 09:48 am, ly...@kn... wrote:
> On Sun, 04 Apr 2004 10:22:47 +0200, Gilles Filippini
>
> <gil...@fr...> wrote :
> > It takes about 60 iterations on may box. But this problems may eventualy
> > be unrelated to FXRuby:
> >
> > - the segfault occurs without any Ruby msg. It's a brutal segfault:
> > ...
> > count = 58
> > count = 59
> > Erreur de segmentation
> > maison:~/devel/bug$
> >
> > - I've run the very same test case using valgrind and it's gone as far
> > as 6000+ before I stop it.
> >
> > Well... I don't know where to look now :/
>
> Is there any possibility at all that some of this machine's memory (RAM) is
> going bad?

Extremely unlikely.  Even if it were the case, your process wouldn't get the
same physical pages to run in each time it starts.

It *could* be memory related, however.  The fact that you can run under
valgrind (which subsumes malloc() and free() with its own functions), is
a big clue.  


> 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
> finally killing it. So I'm fairly sure there is some other problem afoot.

Let me know if it is in FOX or specific to ruby bindings of FOX; if it
is in FOX then I'll try and fix it quickly.  By the way, we're at patchlevel
1.0.51 with the stable version, and since the API is the same I suggest
people run against that instead of the 1.0.28 version.


	Regards!

		- Jeroen


-- 
+----------------------------------------------------------------------------+
| Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+