My system just upgraded itself to wxGtk 2.4.2. I re-built everything, and had no compile errors. The minimal sample worked fine. I haven''t had a chance to do more testing. But, it appears that wxruby is compatible with wxWindows 2.4.2. Kevin
Kevin Smith wrote:> > My system just upgraded itself to wxGtk 2.4.2. I re-built everything, > and had no compile errors. The minimal sample worked fine. I haven''t had > a chance to do more testing. > > But, it appears that wxruby is compatible with wxWindows 2.4.2. > > KevinOk, then after you''ve done a little more testing to confirm, I''ll switch to 2.4.2 (I haven''t had time to do any more debugging since my last email). Curt
Curt Hibbs wrote:>>But, it appears that wxruby is compatible with wxWindows 2.4.2. >> > Ok, then after you''ve done a little more testing to confirm, I''ll switch to > 2.4.2 (I haven''t had time to do any more debugging since my last email).Several other apps work, but anything with a TextCtrl seems to have problems. Some crash with a segfault during the constructor, while others don''t crash until the destructor is invoked. So far, I haven''t had any luck figuring out the cause. The 2.4.2 docs don''t list any changes that should affect something like this. I''m trying to get the debug version of wxWindows installed, but it''s not quite obvious under Debian how that works. Kevin
Kevin Smith wrote:> Several other apps work, but anything with a TextCtrl seems to have > problems. Some crash with a segfault during the constructor, while > others don''t crash until the destructor is invoked.I''m still struggling with this. I reverted to 2.4.1 and confirmed that the three TextCtrl problems I''m having with 2.4.2 are not problems with 2.4.1. The problems are: 1. If you try to create a TextCtrl with a parent of a Frame, it segfaults during the creation. If you create the TextCtrl with a parent of a Panel that has a parent of a Frame, it works. 2. If you invoke TextCtrl#destroy immediately after creating the widget, it segfaults. 3. When exiting a simple app that has a TextCtrl, it segfaults. This appears to be the same case as #2 internally, as the problem happens during the wxTextCtrl destructor. Problem #1 is a segfault inside malloc, called by strdup from gtk code. Problem #2/3 is a segfault inside free, called from wxTextCtrl destructor. I''m mostly just putting this message out there in the hopes that someone might have an idea of something to try. Or, at least, it will remind me of what I''m seeing, and perhaps in the distant future it might help someone who is searching this list archive because they are having a similar problem. There is a fair chance this is GTK-specific, but it''s hard to tell. Sigh. Kevin