I''m having issues with WxRuby segfaulting when it''s dealing
with
external data in one form or another.
I can reliably force WxRuby to crash by
a) Parsing a file with Hpricot into an internal array of
objects and assigning that to an instance variable on a Wx::Frame
b) Running my script in Eclipse in "debug" mode and merely
mousing over the the main Wx::Frame I''ve created
Any suggestions?
P.S. When''s the .39 release for win32 going to be out? I keep
checking
and everyone else gets it but us unlucky saps needing to use a Windows
box at work :(
P H I L I P S C H A L M
WebTeam@nic.bc.ca <mailto:WebTeaM@nic.bc.ca>
Web Developer
North Island College - College Relations
V: 250 334 5000 ext 4661
_______________________________________________
wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users
Hi Philip Philip Schalm wrote:> > I?m having issues with WxRuby segfaulting when it?s dealing with > external data in one form or another. >Thanks for the reports - I''d like to try this again once you have 0.0.39 as this addresses a substantial number of segfault bugs. I hope we''ll have a binary build in the next few days. Covering the different platforms on wxruby takes a team of volunteers and we don''t always have free time at the same time. I''ll post a message to this list once we have a full 0.0.39 release ready.> > I can reliably force WxRuby to crash by > > a) Parsing a file with Hpricot into an internal array of objects and > assigning that to an instance variable on a Wx::Frame > > b) Running my script in Eclipse in ?debug? mode and merely mousing > over the the main Wx::Frame I?ve created >Not passing the buck, but I have had segfaults using Hpricot on its own. Could you post a sample of the html + code, or check that running that Hpricot code itself runs OK outside wxruby - perhaps with GC.start? I would really like to get ''debug'' mode working on Eclipse but it always just hangs for me. Do you have GC.disable at the start of your script, and do you get the same behaviour if you launch the script (with -rdebug) from the command prompt? cheers alex
Hi Alex, It appears that the issues were fixed with the 0.0.39 build of WxRuby, so I''ve got no more problems :D Cheers -----Original Message----- From: wxruby-users-bounces at rubyforge.org [mailto:wxruby-users-bounces at rubyforge.org] On Behalf Of Alex Fenton Sent: Saturday, March 17, 2007 5:39 PM To: General discussion of wxRuby Subject: Re: [Wxruby-users] General segfaulting Hi Philip Philip Schalm wrote:> > I''m having issues with WxRuby segfaulting when it''s dealing with > external data in one form or another. >Thanks for the reports - I''d like to try this again once you have 0.0.39 as this addresses a substantial number of segfault bugs. I hope we''ll have a binary build in the next few days. Covering the different platforms on wxruby takes a team of volunteers and we don''t always have free time at the same time. I''ll post a message to this list once we have a full 0.0.39 release ready.> > I can reliably force WxRuby to crash by > > a) Parsing a file with Hpricot into an internal array of objects and > assigning that to an instance variable on a Wx::Frame > > b) Running my script in Eclipse in "debug" mode and merely mousing > over the the main Wx::Frame I''ve created >Not passing the buck, but I have had segfaults using Hpricot on its own. Could you post a sample of the html + code, or check that running that Hpricot code itself runs OK outside wxruby - perhaps with GC.start? I would really like to get ''debug'' mode working on Eclipse but it always just hangs for me. Do you have GC.disable at the start of your script, and do you get the same behaviour if you launch the script (with -rdebug) from the command prompt? cheers alex _______________________________________________ wxruby-users mailing list wxruby-users at rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users