[wxruby-users] Segmentation Fault.

[Alex Fenton]

Christos Vasilakis wrote:
> Then I tried to:
>
> root at casper:/home/cvasilak/wxruby/wxruby2# ruby 
> /home/cvasilak/helloworld.rb
> /home/cvasilak/helloworld.rb:1:in `require': no such file to load -- wx 
> (LoadError)
>   from /home/cvasilak/helloworld.rb:1
>   
OK, this looks good
> Then I tried to:
>
> root at casper:/home/cvasilak/wxruby/wxruby2# ruby -I lib/ 
> /home/cvasilak/helloworld.rb
> /home/cvasilak/helloworld.rb:4: [BUG] Segmentation fault
> ruby 1.8.6 (2007-09-24) [i486-linux]
>
> Aborted
>
> I tried the second example but this time I get a window but upon exit I 
> receive the segmentation fault.
>
> That's really weird because as you say I use the same configuration as 
> yours(Ubuntu 8.04, 2.8.7 wxwidgets etc). 
I think the only difference is that I'm using a debug build package of 
wxWidgets from Debian (it has the suffix -dbg) rather than the standard 
libwx2.8. But that really shouldn't affect this.

I'd suggest you try doing updating the sources to ensure you're up to 
HEAD (svn up) then doing a clean rebuild (rake reswig; rake). Then try 
running it using the local library (ruby -Ilib ...)

If you're still getting the crash, it would be most useful to get a 
backtrace from gdb debugger.

Try doing:
gdb --args ruby -Ilib helloworld.rb

Then at the gdb prompt:

gdb> r < ENTER>

If it stops after complaining about threads not found:

gdb> c <ENTER>

Then wait until it crashes. gdb should throw out some info. To get a 
full backtrace, do

gdb> whe <ENTER>

This should give a backtrace of where the crash occurred.

thanks for your patience
alex