Re: [Fxruby-users] segfault with FXTreeList in Ruby 1.8.0

[Lyle J. <jl...@cf...>]

Joel VanderWerf wrote:

> Linux Mandrake 9.1. I've never learned to use valgrind (maybe this would 
> be a good excuse to do so :))

Like most tools, valgrind works great for some debugging expeditions and 
not so well for others. But it is not too hard to use (no recompilation 
or other "instrumentation" of your code required) and is a good one to 
be familiar with.

> As you point out, this is very strange. The pc at frame #4 is inside the 
> DataGetStruct(obj, ...) macro, which calls rb_check_type() with obj as 
> the first arg. But at that point the value has been clobbered somehow.
> 
> I'll give valgrind a shot...

OK, let me know if I need to take a look at it. I just went back and ran 
'stress1.rb', one of the stress test cases from the FXRuby/tests 
subdirectory and it seemed to hold up fine. [That one basically creates 
and then trashes a large number of tree items, trying to smoke out 
GC-related problems.]