Hi Think I tracked down why Windows suddenly went horrible crashy - the newest SWIG release generates slightly different code for object tracking, so our fixmodule.rb wasn''t picking up the broken line, so we got a nasty regression. Anyway, the patch (SVN:862) gives me a major improvement in stability Windows. Please could you let me know how SVN HEAD is working for you; if no major probs I''d like to release 0.0.39. cheers alex
Alex Fenton wrote:> Think I tracked down why Windows suddenly went horrible crashy - the > newest SWIG release generates slightly different code for object > tracking, so our fixmodule.rb wasn''t picking up the broken line, so we > got a nasty regression.Sure would be nice if we could persuade upstream SWIG to add the features that we are having to fake like this. It seems pretty reasonable to want to construct a SWIG app with multiple .cpp files, for example. Kevin P.S. Briefly crawling out from under a rock, before I dive back in. Apologies for my ongoing absence. I''m REALLY glad you guys are continuing to do a great job with wxruby!
Hey Kevin don''t feel bad I literally have 10 minutes a day for wxRuby which I spend reading the mailing lists. I don''t know where Alex finds the time to do all his contributions, but hats off to him. Glad to see you making an appearance! Sean On 2/14/07, Kevin Smith <wxruby at qualitycode.com> wrote:> Alex Fenton wrote: > > Think I tracked down why Windows suddenly went horrible crashy - the > > newest SWIG release generates slightly different code for object > > tracking, so our fixmodule.rb wasn''t picking up the broken line, so we > > got a nasty regression. > > Sure would be nice if we could persuade upstream SWIG to add the > features that we are having to fake like this. It seems pretty > reasonable to want to construct a SWIG app with multiple .cpp files, for > example. > > Kevin > > P.S. Briefly crawling out from under a rock, before I dive back in. > Apologies for my ongoing absence. I''m REALLY glad you guys are > continuing to do a great job with wxruby! > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Alex Fenton wrote:> Hi > > Think I tracked down why Windows suddenly went horrible crashy - the > newest SWIG release generates slightly different code for object > tracking, so our fixmodule.rb wasn''t picking up the broken line, so we > got a nasty regression. > > Anyway, the patch (SVN:862) gives me a major improvement in stability > Windows. Please could you let me know how SVN HEAD is working for you; > if no major probs I''d like to release 0.0.39. > >Hi Alex. I had a few free minutes so I download the updates and compiled. It seems OK but my example of running the gauge demo still crashes it after running a few seconds (not moving the mouse pointer). Could be another crash entirely. From your comments it sounds like you''ve figured out a way to debug this or at least trace back the crashes. This is something I''ve never managed on Windows. Can you tell me what you did? Roy
Hi> Hi Alex. I had a few free minutes so I download the updates and > compiled. It seems OK but my example of running the gauge demo still > crashes it after running a few seconds (not moving the mouse pointer). >Thanks for testing - i''m not seeing that error - gauge sample seems to run fine for several minutes, and survive GC. Did you do a full reswig and clean build?> From your comments it sounds like you''ve figured out a way to debug > this or at least trace back the crashes. This is something I''ve never > managed on Windows. Can you tell me what you did? >I''ve been using WinDebug, which is a free MS download from: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx All I''ve been doing is getting stack traces, which it presents fairly well. Basically, I - launch the demo at the command line - hit F6 in the debugger, find the ruby process and attach to it - hit F5 in the debugger to restart the process - wait for a crash... I tried mingw first, but I''ve been using the current free VS compiler. I don''t think it''s recommended for use with the one-click ruby because of binary compatibility probs, but haven''t found any weird errors yet. cheers alex
Kevin Smith wrote:> Sure would be nice if we could persuade upstream SWIG to add the > features that we are having to fake like this. >I agree; the fix__.rb scripts are a great piece of detective work but can''t help but be fragile and complex. I was a bit disappointed that some of the fixes Roy submitted didn''t make it into 1.3.31. I don''t have time to track the SWIG list, but might try submitting this one through sourceforge and see what happens.> P.S. Briefly crawling out from under a rock, before I dive back in. > Apologies for my ongoing absence. I''m REALLY glad you guys are > continuing to do a great job with wxruby! >Thanks, and no apology needed. We''re lucky that you''d already solved the really hard problems! Best wishes aelx
Alex Fenton wrote:> Hi > >> Hi Alex. I had a few free minutes so I download the updates and >> compiled. It seems OK but my example of running the gauge demo still >> crashes it after running a few seconds (not moving the mouse pointer). >> >> > Thanks for testing - i''m not seeing that error - gauge sample seems to > run fine for several minutes, and survive GC. Did you do a full reswig > and clean build? >I thought so... I''ll re-check.>> From your comments it sounds like you''ve figured out a way to debug >> this or at least trace back the crashes. This is something I''ve never >> managed on Windows. Can you tell me what you did? >> >> > I''ve been using WinDebug, which is a free MS download from: > http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx > > All I''ve been doing is getting stack traces, which it presents fairly > well. Basically, I > - launch the demo at the command line > - hit F6 in the debugger, find the ruby process and attach to it > - hit F5 in the debugger to restart the process > - wait for a crash... > >Hmm, when I try this it never finds the symbols. I''ll see what WinDebug is, I don''t have that. It could be some conflicts with other debuggers I have installed. Roy
Roy Sutton wrote:> Alex Fenton wrote: >> - launch the demo at the command line >> - hit F6 in the debugger, find the ruby process and attach to it >> - hit F5 in the debugger to restart the process >> - wait for a crash... >> >> >> > Hmm, when I try this it never finds the symbols. I''ll see what WinDebug > is, I don''t have that. It could be some conflicts with other debuggers > I have installed. >Frustrating innit ... can''t remember how I fixed it; maybe it''s only worked properly since I installed VS Express. With the SDK and installers it''s hard to know what comes with what... alex