This is a follow up to my Feb 18 post on the Ruby forum: Are others experiencing problems using FXRuby on 64-bit Windows platforms? I have an FXRuby app that works fine on 32-bit Windows XP, but has random segmentation faults and other errors on a 64-bit Windows 7 platform. I''ve attached a screen shot of the typical errors that I get. The application will run for a time, but eventually will crash with a segmentation fault. Also, there are numerous FXCursor.cpp errors that appear as the application is starting (but the application still starts and runs despite these initial errors). Again, this only happens on the 64-bit system. The same app works with no errors on a 32-bit Windows OS. Lyle had responded to my earlier post indicating that it seems to be an issue with the FOX Library itself, not the FXRuby wrapper. I see on the FOX Library webpage that over the past year or two they''ve addressed some 64 vs 32 bit issues. Does FXRuby use the latest version of the FOX library? If not, will the newer version of the FOX Library solve these issues? Are there any workarounds? --Alex DeCaria -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100302/6d960234/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Error.jpg Type: image/pjpeg Size: 296421 bytes Desc: Error.jpg URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100302/6d960234/attachment-0001.bin>
On Tue, Mar 2, 2010 at 6:49 AM, Alex DeCaria <Alex.Decaria at millersville.edu> wrote:> Lyle had responded to my earlier post indicating that it seems to be an > issue with the FOX Library itself, not the FXRuby wrapper.? I see on the FOX > Library webpage that over the past year or two they''ve addressed some 64 vs > 32 bit issues.? Does FXRuby use the latest version of the FOX library?The binary gem for FXRuby version 1.6.20 on Windows is built with FOX 1.6.36, which is close to the latest release (version 1.6.37). I don''t see anything in the release notes for 1.6.37 that sound like they would address this problem, though.> Are there any workarounds?That''s hard to say without really knowing what''s going on. It''s usually helpful in cases like this to post some code that reproduces the problem, so that anyone who''s interested can at least attempt to diagnose the problem. If I can reproduce it on my Mac OS X notebook, I might be able to come up with a fix, but I don''t even have access to a 64-bit Windows environment for testing your particular configuration.
I have to amend my earlier statement. The program just exhibited the same behavior on my 32-bit Windows OS, so it''s obviously not an OS issue, and likely due to my own faulty programming skills. This is my first attempt at an FXRuby application (I''m converting from TK) and I''m not doing something correctly. The application runs just fine for a while, but after enough use (clicking on various list boxes) eventually gives the segmentation error. I''ve attached it in case anyone is bored enough and has the time/inclination to look at it and can give me some pointers as to how to clean it up and use a better programming idiom. The code is ugly, I know, because it is my first try. Sorry for my original mistake of thinking it was the OS. --Alex -----Original Message----- From: fxruby-users-bounces at rubyforge.org [mailto:fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson Sent: Tuesday, March 02, 2010 2:44 PM To: fxruby-users at rubyforge.org Subject: Re: [fxruby-users] FXRuby and 64-Bit Windows OS On Tue, Mar 2, 2010 at 6:49 AM, Alex DeCaria <Alex.Decaria at millersville.edu> wrote:> Lyle had responded to my earlier post indicating that it seems to be an > issue with the FOX Library itself, not the FXRuby wrapper.? I see on the FOX > Library webpage that over the past year or two they''ve addressed some 64 vs > 32 bit issues.? Does FXRuby use the latest version of the FOX library?The binary gem for FXRuby version 1.6.20 on Windows is built with FOX 1.6.36, which is close to the latest release (version 1.6.37). I don''t see anything in the release notes for 1.6.37 that sound like they would address this problem, though.> Are there any workarounds?That''s hard to say without really knowing what''s going on. It''s usually helpful in cases like this to post some code that reproduces the problem, so that anyone who''s interested can at least attempt to diagnose the problem. If I can reproduce it on my Mac OS X notebook, I might be able to come up with a fix, but I don''t even have access to a 64-bit Windows environment for testing your particular configuration. _______________________________________________ fxruby-users mailing list fxruby-users at rubyforge.org http://rubyforge.org/mailman/listinfo/fxruby-users -------------- next part -------------- A non-text attachment was scrubbed... Name: unit_converter_FX.rb Type: application/octet-stream Size: 12224 bytes Desc: unit_converter_FX.rb URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100302/7a797107/attachment-0001.obj>