[wxruby-users] Segmentation Fault.

[Alex Fenton]

Hi

Christos Vasilakis wrote:
> I get the segmentation fault. Then I tried running it with gdb as you 
> suggested:
>
> gdb --args ruby -I lib /home/cvasilak/helloworld.rb
> ....
> ....
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb7d29b60 (LWP 9022)]
> 0xb5f6bf74 in ?? () from /lib/libselinux.so.1
> (gdb) whe
> #0  0xb5f6bf74 in ?? () from /lib/libselinux.so.1
> #1  0xb5f6564e in ?? () from /lib/libselinux.so.1
> #2  0xb5f5e100 in ?? () from /lib/libselinux.so.1
> #3  0xb5f6d7bc in _fini () from /lib/libselinux.so.1
> #4  0xb7fe0fdf in ?? () from /lib/ld-linux.so.2
> #5  0xb7d58084 in exit () from /lib/tls/i686/cmov/libc.so.6
> #6  0xb7f1ec85 in ruby_stop () from /usr/lib/libruby1.8.so.1.8
> #7  0xb7f29cf1 in ruby_run () from /usr/lib/libruby1.8.so.1.8
> #8  0x080486bd in main ()
> (gdb)
>
>   

Thanks for running this. Unfortunately it seems that the debugging 
information has got truncated - I guess because you are using a release 
build of wxWidgets, and thus wxRuby tries to compile the smallest, 
fastest possible.

If you were willing to try reproducing the error in a debug build, that 
should give more information. There is libwx package in Ubuntu with the 
-dbg suffix. If you install this, then run

export WXRUBY_DEBUG=1
rake reswig
rake

and then try re-running the same process, we should get a more helpful 
backtrace. This is really puzzling as you have almost exactly the same 
setup as me, except that i built my own ruby.

thanks
alex