[fxruby-users] crash analysis

Andreas Schmidt watobo at siberas.de
Thu Sep 26 06:57:58 UTC 2013

Hi together,

I get the following error when I close my fxruby application:

watobo_gui.rb: [BUG] Segmentation fault
ruby 1.9.3p448 (2013-06-27) [i386-mingw32]

-- Control frame information -----------------------------------------------
c:0001 p:0000 s:0002 b:0002 l:00182c d:00182c TOP

-- C level backtrace information -------------------------------------------
C:\Windows\SysWOW64\ntdll.dll(ZwWaitForSingleObject+0x15) [0x77e4f8d1]
C:\Windows\syswow64\kernel32.dll(WaitForSingleObjectEx+0x43) [0x762b1194]
C:\Windows\syswow64\kernel32.dll(WaitForSingleObject+0x12) [0x762b1148]
C:\Ruby193\bin\msvcrt-ruby191.dll(rb_vm_bugreport+0xf9) [0x62e5bec5]
C:\Ruby193\bin\msvcrt-ruby191.dll(rb_name_err_mesg_new+0x17a) [0x62d3a87a]
C:\Ruby193\bin\msvcrt-ruby191.dll(rb_bug+0x2f) [0x62d3b557]
C:\Ruby193\bin\msvcrt-ruby191.dll(rb_check_safe_str+0x194) [0x62dee898]
C:\Program Files\ThinkPad\Bluetooth
mHook+0xfac9) [0x10013989]
C:\Windows\SysWOW64\ntdll.dll(RtlKnownExceptionFilter+0xb7) [0x77ea74ff]

Is this a thread problem? Because I use threads, but not for updating
the gui. I use Queues and Mutexes inside fxruby Timeouts (addTimeout).
Are there any limitations?

Is there an easy way to narrow it down to the responsible code? Because
I don't get any debug messages when the program is running in debug-mode
(-d). I only get the crash when I close the program.



More information about the fxruby-users mailing list