[wxruby-users] Segmentation Fault : [i386-mswin32] in wxruby

Alex Fenton alex at pressure.to
Tue Jan 13 04:03:20 EST 2009


Lc Yeap wrote:
> However, when I run my program again, the same error occurred. --> 
> "config_vector_v6.rb:1418: [BUG] Segmentation fault
> ruby 1.8.6 (2007-09-24) [i386-mswin32]"
>   

You can check what version of wxRuby is being used by your program by 
looking at the value of Wx::WXRUBY_VERSION. It's printed out in the 
"About" box of the minimal sample.
> so I deleted the previous gem "wxruby-1.9.7-i386-mswin32.gem" from the 
> bin folder and reinstalled it again, but still the same error being 
> reported.
>   

Use gem uninstall, don't delete directly.


> I tried with command "gem update wxruby" but I get this-->"ERROR:  While 
> executing gem ... (Gem::RemoteFetcher::FetchError)
>     No connection could be made because the target machine actively 
> refused it.
> - connect(2)(Errno::ECONNREFUSED)"
>   

Make sure that you have the latest versions of rubygems installed then 
try installing wxruby-1.9.9 again.

gem --update system


> Is that I am not using the correct version of wxruby? can you point me 
> how to upgrade my wxruby? If this still fail again after using wxruby 
> 1.9.9, I will attach a sample code of my program.

OK. It might be worth posting a runnable sample of your code anyway. 
There may be something in there obvious that's not quite right - 
although wxRuby tries to raise an exception on incorrect use of the API, 
this isn't always possible. Or if there is a bug, it may still exist in 
the latest development version, in which case sample code will help us 
find it quicker.

a


More information about the wxruby-users mailing list