From chauk.mean at gmail.com Mon Sep 1 05:50:03 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Mon, 1 Sep 2008 11:50:03 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: Message-ID: Hi, I solved the problem I had regarding building wxRuby and wxWidgets. 2008/8/31 Chauk-Mean P : > D/ Building myself wxRuby for Ruby 1.9.0-4 : > For my previous build of wxRuby and bug report, I used the wxWidgets > 2.8.7 package provided with Ubuntu. > As it seems that wxWidgets 2.8.8 fixes some issues with wxRuby, I > tried now a full build of wxWidgets and wxRuby. > Building wxWidgets and wxRuby as indicated in the wiki work fine > But when I run a sample, I have a problem with undefined references > related with gstreamer. The problem is caused by the fact that the wxruby.so is not linked with gstreamer libs. I modified the rake/rakelinux.rb file by adding : -lgstreamer-0.10 -lgstinterfaces-0.10 to the $extralibs variable. Now I can run samples. Cheers. Chauk-Mean. From chauk.mean at gmail.com Mon Sep 1 07:55:37 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Mon, 1 Sep 2008 13:55:37 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: Message-ID: Hi again, Here are additional feedbacks again on Linux Ubuntu 8.04 x86 : - Each time an application exits, a segmentation fault occurs - I have exactly the same problems with Ruby 1.9.0-4 as with Ruby 1.8.4-p72 including the segmentation fault upon an application exit - I have been able to run wxRuby from the build directory (e.g. ruby -Ilib samples/bigdemo/bigdemo.rb) with both Ruby 1.8.4-p72 and Ruby 1.9.0-4 but the built gem seems to be broken. When I try to install the gem the following error is reported : ERROR: While executing gem ... (ArgumentError) string contains null byte Cheers. Chauk-Mean. From noreply at rubyforge.org Thu Sep 4 12:24:04 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 4 Sep 2008 12:24:04 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Bugs-21811 ] Crashes with ScrolledWindow under Linux Message-ID: <20080904162404.923A318585BC@rubyforge.org> Bugs item #21811, was opened at 2008-09-04 16:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21811&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Crashes with ScrolledWindow under Linux Initial Comment: This is demonstrated with 1.9.8 in the SCrolledWindow example. Scrolling the window quickly gives the following error: The Program 'wxruby' received an X Window System error. This probably reflects a bug in the program This error was 'BadValue (integer parameter out of range for operation)' (Details: serial 4589 error_code 2 request_code 58 minor_code 0) Originally reported in this thread: http://rubyforge.org/pipermail/wxruby-development/2008-August/001379.html ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21811&group_id=35 From alex at pressure.to Thu Sep 4 12:59:23 2008 From: alex at pressure.to (Alex Fenton) Date: Thu, 04 Sep 2008 17:59:23 +0100 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: Message-ID: <48C013EB.6060805@pressure.to> Hi Chauk-Mean P wrote: > I've just tested wxRuby 1.9.8 on Windows and Linux Ubuntu 8.04 x86. > Thanks for these detailed notes. Sorry for taking some time to reply but I've been concentrating on getting a working mswin32 build. > B/ On Linux Ubuntu 8.04 x86 + Ruby 1.8.7-p72 : > I used the linux gem. It works better than my previous test but I > still have the following problems with the bigdemo : > > 1/ bigdemo > Base Frames and Dialogs > wxMDIWindows : > - Create a child window (File > New Window) > - Use the scrollbars (especially the vertical one) to move the > contents of the child window > => crash. This is not related with MDI but rather with the code of > the child window which uses scrollbars. > > 2/ bigdemo > Core Windows/Controls > wxScrolledWindow > - Use the scrollbars to move the contents of the window > => crash. This is probably the same problem as above. > These are the same crash. I don't really know what the error message means. I've filed it as a bug, must fix for 2.0 > 3/ bigdemo > Common Dialogs > wxFindReplaceDialog > Show Find Dialog > or > bigdemo > Common Dialogs > wxFindReplaceDialog > Show Find and > Replace Dialog : > - Type some text > - Click Find > => > Can reproduce this too; have got a debugging trace so should be OK to fix. > C/ On Linux Ubuntu 8.04 x86 + Ruby 1.9.0-4 : > I tried to use the wxruby-ruby19 linux gem. But this gem is broken ! > In the lib folder, there is only the shared library ! > > Oh, I should have tested this. I can't get it to work either. Not sure if the way gems works has changed in 1.9 as it is now built-in. > D/ Building myself wxRuby for Ruby 1.9.0-4 : > For my previous build of wxRuby and bug report, I used the wxWidgets > 2.8.7 package provided with Ubuntu. > As it seems that wxWidgets 2.8.8 fixes some issues with wxRuby, I > tried now a full build of wxWidgets and wxRuby. > Building wxWidgets and wxRuby as indicated in the wiki work fine > (wxWidgets with monolithic, disable shared, enable mediactrl ...) > But when I run a sample, I have a problem with undefined references > related with gstreamer. Mmmm, I would have expected wx-config to sort out the correct linker flags that you describe as the solution in your later post. From noreply at rubyforge.org Thu Sep 4 13:03:09 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 4 Sep 2008 13:03:09 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Bugs-21812 ] FindReplaceDialog crashing on Linux Message-ID: <20080904170310.1332D18581A8@rubyforge.org> Bugs item #21812, was opened at 2008-09-04 17:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21812&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: FindReplaceDialog crashing on Linux Initial Comment: Steps to reproduce: 3/ bigdemo > Common Dialogs > wxFindReplaceDialog > Show Find Dialog or bigdemo > Common Dialogs > wxFindReplaceDialog > Show Find and Replace Dialog : - Type some text - Click Find => crash after one or several clicks or : - Just Click Cancel - Show again the dialog - Click again Cancel => crash gdb points this to a failure in OnFind Originally reported in this message: http://rubyforge.org/pipermail/wxruby-development/2008-August/001379.html ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21812&group_id=35 From chauk.mean at gmail.com Fri Sep 5 09:41:37 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Fri, 5 Sep 2008 15:41:37 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: <48C013EB.6060805@pressure.to> References: <48C013EB.6060805@pressure.to> Message-ID: Hi Alex, 2008/9/4 Alex Fenton : > These are the same crash. I don't really know what the error message means. > I've filed it as a bug, must fix for 2.0 > > ... > Can reproduce this too; have got a debugging trace so should be OK to fix. > It's a good thing that you have been able to reproduce these issues. Have you taken a look at the 2 last issues I reported (http://rubyforge.org/pipermail/wxruby-development/2008-September/001381.html) : - the seg fault at an application exit (e.g. the minimal demo). This is very annoying. - the 'string contains null byte' problem I have when I try to install a built gem Cheers. Chauk-Mean. From alex at pressure.to Fri Sep 5 17:25:26 2008 From: alex at pressure.to (Alex Fenton) Date: Fri, 05 Sep 2008 22:25:26 +0100 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> Message-ID: <48C1A3C6.80208@pressure.to> Chauk-Mean P wrote: > Have you taken a look at the 2 last issues I reported > (http://rubyforge.org/pipermail/wxruby-development/2008-September/001381.html) > : > - the seg fault at an application exit (e.g. the minimal demo). This > is very annoying. > I can't reproduce this on Linux (Ubuntu 8.04) with either the 1.9.8 gem or my HEAD debug build. Tried minimal, bigdemo, controls. Is it possible to get a backtrace using gdb if you have a debug build available? On Ubuntu there is a -dbg package available in the repository. > - the 'string contains null byte' problem I have when I try to install > a built gem I installed the ruby19 gem like this: sudo gem install wxruby-ruby19 This completes OK, but as you pointed out, there is only the shared .so lib in the linux gem. I looked again at the original build tree and it seems its a fault with the packaging. I've withdrawn this download for now. Strangely the OS-X 1.9 gem is fine and has all the expected contents. thanks alex From chauk.mean at gmail.com Sat Sep 6 04:19:01 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Sat, 6 Sep 2008 10:19:01 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: <48C1A3C6.80208@pressure.to> References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> Message-ID: Hi Alex, > I can't reproduce this on Linux (Ubuntu 8.04) with either the 1.9.8 gem or > my HEAD debug build. Tried minimal, bigdemo, controls. Is it possible to get > a backtrace using gdb if you have a debug build available? On Ubuntu there > is a -dbg package available in the repository. I have the crash with both the official build of wxruby 1.9.8 and a build made by myself. So I rebuilt wxWidgets in debug mode and also rebuilt wxruby. Then I run the minimal demo : chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ulimit -c unlimited chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ruby -Ilib samples/minimal/minimal.rb Calling wxEntry, this=0x81b7548 OnExit... ~wxRubyApp returned from wxEntry... === Starting App GC mark phase === App has ended, skipping mark phase survived gc /opt/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: [BUG] Segmentation fault ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-linux] Aborted (core dumped) chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ I open the core file from GDB and I got : chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ gdb -c core GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu". (no debugging symbols found) Core was generated by `ruby -Ilib samples/minimal/minimal.rb'. Program terminated with signal 6, Aborted. [New process 9022] #0 0xb7fba410 in __kernel_vsyscall () (gdb) bt #0 0xb7fba410 in __kernel_vsyscall () #1 0xb7e2a085 in ?? () (gdb) I hope that this helps. Note also that I have the same crash with the official Ubuntu ruby (1.8.6-p111) + rubygems (1.1.1 and 1.2.0) + official wxruby (1.9.7 and 1.9.8). >> - the 'string contains null byte' problem I have when I try to install >> a built gem > This completes OK, but as you pointed out, there is only the shared .so lib > in the linux gem. I looked again at the original build tree and it seems its > a fault with the packaging. I've withdrawn this download for now. I don't have this 'string contains null byte' problem with official wxruby gems. I have the problem only with gems I built myself from the source. Thanks. Chauk-Mean. From alex at pressure.to Sat Sep 6 11:13:17 2008 From: alex at pressure.to (Alex Fenton) Date: Sat, 06 Sep 2008 16:13:17 +0100 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> Message-ID: <48C29E0D.9020607@pressure.to> Chauk-Mean P wrote: > I have the crash with both the official build of wxruby 1.9.8 and a > build made by myself. > So I rebuilt wxWidgets in debug mode and also rebuilt wxruby. > Then I run the minimal demo : > > chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ulimit -c unlimited > chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ruby -Ilib samples/minimal/minimal.rb > Calling wxEntry, this=0x81b7548 > OnExit... > ~wxRubyApp > returned from wxEntry... > === Starting App GC mark phase > === App has ended, skipping mark phase > survived gc > /opt/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: [BUG] > Segmentation fault > ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-linux] > > I'm running ruby 1.8.7 2008-08-08 patchlevel 70 but it seems unlikely that's the difference. Also it's geting to the very end of the cleanup; usually crash-on-exit occurs earlier. ... > [New process 9022] > #0 0xb7fba410 in __kernel_vsyscall () > (gdb) bt > #0 0xb7fba410 in __kernel_vsyscall () > #1 0xb7e2a085 in ?? () > (gdb) > Thanks for running this. Unfortunately the backtrace seems to be truncated. Can you try running it like this, ensuring that you're loading the WXRUBY_DEBUG version of the library? gdb --args ruby -Ilib samples/minimal/minimal.rb gdb> r .... wait for crash ... gdb> whe ... should give backtrace. > Note also that I have the same crash with the official Ubuntu ruby > (1.8.6-p111) + rubygems (1.1.1 and 1.2.0) + official wxruby (1.9.7 and > 1.9.8). > If you get it with 1.9.7, then it rules out one thing I was thinking of. And if it's with 1.8.6, it seems unlikely to be something specific to recent changes in ruby. Hmmm. > I don't have this 'string contains null byte' problem with official > wxruby gems. > I have the problem only with gems I built myself from the source. > I'm afraid I can't reproduce this. As an alternative you can use the rake install / rake uninstall targets, or use the official builds. cheers alex From noreply at rubyforge.org Sat Sep 6 14:37:45 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 6 Sep 2008 14:37:45 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Feature Requests-21843 ] support wxMozilla Message-ID: <20080906183745.BC9B518581B8@rubyforge.org> Feature Requests item #21843, was opened at 2008-09-06 13:37 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21843&group_id=35 Category: None Group: None Status: Open Priority: 3 Submitted By: Tulnor Belefaroth (ppibburr) Assigned to: Nobody (None) Summary: support wxMozilla Initial Comment: will wxruby ever support wxMozilla ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21843&group_id=35 From noreply at rubyforge.org Sat Sep 6 15:28:57 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 6 Sep 2008 15:28:57 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Feature Requests-21844 ] Add wxStandardPaths Message-ID: <20080906192857.3E268185859F@rubyforge.org> Feature Requests item #21844, was opened at 2008-09-06 19:28 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21844&group_id=35 Category: Missing class(es) Group: None Status: Open Priority: 3 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Add wxStandardPaths Initial Comment: Provides useful access to standard OS paths. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21844&group_id=35 From mario at ruby-im.net Sat Sep 6 19:52:05 2008 From: mario at ruby-im.net (Mario Steele) Date: Sat, 6 Sep 2008 18:52:05 -0500 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: <48C29E0D.9020607@pressure.to> References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: Actually, I get the crash on exit with my app, and I think it's again the culprit of SELinux that is causing the problem, cause when I run the core dump through GDB, it gives SELinux as the culprit just before the __kernel_vsyscall(). On Sat, Sep 6, 2008 at 10:13 AM, Alex Fenton wrote: > Chauk-Mean P wrote: > >> I have the crash with both the official build of wxruby 1.9.8 and a >> build made by myself. >> So I rebuilt wxWidgets in debug mode and also rebuilt wxruby. >> Then I run the minimal demo : >> >> chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ulimit -c unlimited >> chauk-mean at MyLinuxBox:~/wxruby-1.9.8$ ruby -Ilib >> samples/minimal/minimal.rb >> Calling wxEntry, this=0x81b7548 >> OnExit... >> ~wxRubyApp >> returned from wxEntry... >> === Starting App GC mark phase >> === App has ended, skipping mark phase >> survived gc >> /opt/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: [BUG] >> Segmentation fault >> ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-linux] >> >> >> > I'm running ruby 1.8.7 2008-08-08 patchlevel 70 but it seems unlikely > that's the difference. Also it's geting to the very end of the cleanup; > usually crash-on-exit occurs earlier. > > ... > > [New process 9022] >> #0 0xb7fba410 in __kernel_vsyscall () >> (gdb) bt >> #0 0xb7fba410 in __kernel_vsyscall () >> #1 0xb7e2a085 in ?? () >> (gdb) >> >> > Thanks for running this. Unfortunately the backtrace seems to be truncated. > > Can you try running it like this, ensuring that you're loading the > WXRUBY_DEBUG version of the library? > > gdb --args ruby -Ilib samples/minimal/minimal.rb > gdb> r > .... wait for crash ... > gdb> whe > ... should give backtrace. > > Note also that I have the same crash with the official Ubuntu ruby >> (1.8.6-p111) + rubygems (1.1.1 and 1.2.0) + official wxruby (1.9.7 and >> 1.9.8). >> >> > If you get it with 1.9.7, then it rules out one thing I was thinking of. > And if it's with 1.8.6, it seems unlikely to be something specific to recent > changes in ruby. Hmmm. > > I don't have this 'string contains null byte' problem with official >> wxruby gems. >> I have the problem only with gems I built myself from the source. >> >> > I'm afraid I can't reproduce this. As an alternative you can use the rake > install / rake uninstall targets, or use the official builds. > > cheers > alex > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > -- Mario Steele http://www.trilake.net http://www.ruby-im.net http://rubyforge.org/projects/wxruby/ http://rubyforge.org/projects/wxride/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex at pressure.to Sat Sep 6 19:59:19 2008 From: alex at pressure.to (Alex Fenton) Date: Sun, 07 Sep 2008 00:59:19 +0100 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: <48C31957.90007@pressure.to> Mario Steele wrote: > Actually, I get the crash on exit with my app, and I think it's again > the culprit of SELinux that is causing the problem, cause when I run > the core dump through GDB, it gives SELinux as the culprit just before > the __kernel_vsyscall(). Thanks Mario - is there any way around this? Something we need to do to avoid crashing? cheers alex From chauk.mean at gmail.com Mon Sep 8 03:42:27 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Mon, 8 Sep 2008 09:42:27 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: Hi Mario, 2008/9/7 Mario Steele : > Actually, I get the crash on exit with my app, and I think it's again the > culprit of SELinux that is causing the problem, cause when I run the core > dump through GDB, it gives SELinux as the culprit just before the > __kernel_vsyscall(). I'm feeling less lonely :-). It's great that you have been able to identify the source of the problem. Cheers. Chauk-Mean. From noreply at rubyforge.org Fri Sep 12 10:49:38 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 12 Sep 2008 10:49:38 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Bugs-21933 ] warning: Unmapped event type 10092 Message-ID: <20080912144938.92E5D18581A8@rubyforge.org> Bugs item #21933, was opened at 2008-09-12 10:49 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21933&group_id=35 Category: Missing API call Group: current Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: warning: Unmapped event type 10092 Initial Comment: Hello, I recently upgraded to current and now I'm getting this warning: `warning: Unmapped event type 10092` By using the following code: `require 'wx'; a=Wx.constants.grep(/evt/i).find { |x| (eval('Wx::' + x) == 10092) }; puts a` This turns out to be `EVT_NAVIGATION_KEY`, and this warning is printed when I push the tab key to get around in my application. I fixed the warning by doing: `Wx::EvtHandler::EVENT_TYPE_CLASS_MAP[10092] = Wx::KeyEvent` Though I've been informed on ruby-talk that the correct class would be `Wx::NavigationKeyEvent`, which doesn't currently exist in WxRuby. Just as an aside, I use Windows Vista at work (where I code) and as of a Windows Update yesterday, my WxRuby applications all have the Vista theme. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21933&group_id=35 From niklas.baumstark at googlemail.com Mon Sep 15 12:08:53 2008 From: niklas.baumstark at googlemail.com (Niklas Baumstark) Date: Mon, 15 Sep 2008 18:08:53 +0200 Subject: [wxruby-development] Init_wxruby2 issue when called twice in the same program Message-ID: <20080915180853.55eb7170@niklaspc> Hello, i ran into the following issue while trying to setup my C++ wxWidgets program for embedded ruby code. reproduce: add the following to a button event handler of a running wxWidgets application linked to wxruby2.so: ===================== extern "C" void Init_wxruby2(); ... ruby_init(); ruby_init_loadpath(); rb_eval_string(" $: << 'src' "); ruby_script("embed"); Init_wxruby2(); ruby_finalize(); ... ===================== now click the button twice. a segmentation fault should occur, at least it does on my machine (Ubuntu 8.04, ruby 1.8.7 (2008-08-02 revision 0), wxWidgets 2.8.7, wxRuby 1.9.8 SVN yesterday). i figured out that the line rb_define_const(mWxruby2, "VERSION_STRING", SWIG_FromCharPtr("wxRuby2")); at the end of the Init_wxruby2 causes the error, so i wrapped it into a rb_protect and got the following error: class: SystemStackError message: stack level too deep backtrace: from embed:0:in `write' this error occurs every time a global constant is re-defined (even if the interpreter has been restarted in the meanwhile). Unfortunately i can't test if this problem occurs in a newer version of ruby. maybe someone could test just the following code in a standard c file? #include "ruby.h" void main() { for (int i = 0; i++; i <= 1) { ruby_init(); ruby_init_loadpath(); ruby_script("embed"); rb_define_global_const("TEST", Qnil); ruby_finalize(); } } is there a better way to shut down the interpreter apart from ruby_finalize? Greetings, Niklas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From noreply at rubyforge.org Tue Sep 16 10:29:09 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 16 Sep 2008 10:29:09 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Feature Requests-21982 ] Add INSTALL.txt Message-ID: <20080916142910.38B6B18581B8@rubyforge.org> Feature Requests item #21982, was opened at 2008-09-16 14:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21982&group_id=35 Category: Documentation Group: None Status: Open Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Add INSTALL.txt Initial Comment: Collate all the installation info on the Wiki into an install.txt to go with the source distribution. Cover: * Binary or Build? * Prerequisites * How to Build Wx ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=21982&group_id=35 From noreply at rubyforge.org Tue Sep 16 10:56:38 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 16 Sep 2008 10:56:38 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Bugs-21985 ] Intermittent errors with the Scintilla demo Message-ID: <20080916145638.4324A18585E5@rubyforge.org> Bugs item #21985, was opened at 2008-09-16 14:56 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21985&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Intermittent errors with the Scintilla demo Initial Comment: http://rubyforge.org/pipermail/wxruby-users/2008-September/004175.html I got the following error when I was randomly clicking margins and lines in a StyledTextControl (3 margins). It doesn't occur often, usually happens after many clicks (20 or so). Expected argument 1 of type int, but got Wxruby2::Point # in SWIG method 'LineFromPosition' My env: wxRuby mingw32 1.9.8, ruby 1.8.6 p287 on XP ----- AF: Confirmed with the same environment using the standard scintilla sample. What seems to be happening is that sometimes the event handler is getting passed a Wx::Rect, instead of a Wx::StyledTextEvent, and so the wrong value is returned by get_position. Probably a memory management prob - Rectangles not cleaned up properly? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=21985&group_id=35 From chauk.mean at gmail.com Sat Sep 20 07:27:49 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Sat, 20 Sep 2008 13:27:49 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: Hi, >2008/9/7 Mario Steele : >> Actually, I get the crash on exit with my app, and I think it's again the >> culprit of SELinux that is causing the problem, cause when I run the core >> dump through GDB, it gives SELinux as the culprit just before the >> __kernel_vsyscall(). Here is the backtrace when I run the minimal sample from gdb : gdb --args ruby -Ilib samples/minimal/minimal.rb GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) r Starting program: /opt/bin/ruby -Ilib samples/minimal/minimal.rb [Thread debugging using libthread_db enabled] Error while reading shared library symbols: Cannot find new threads: generic error Cannot find new threads: generic error (gdb) c Continuing. Calling wxEntry, this=0x81fe848 [New Thread 0xb7e1e8c0 (LWP 29321)] OnExit... ~wxRubyApp returned from wxEntry... === Starting App GC mark phase === App has ended, skipping mark phase survived gc Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7e1e8c0 (LWP 29321)] 0xb589af74 in ?? () from /lib/libselinux.so.1 (gdb) whe #0 0xb589af74 in ?? () from /lib/libselinux.so.1 #1 0xb589464e in ?? () from /lib/libselinux.so.1 #2 0xb588d100 in ?? () from /lib/libselinux.so.1 #3 0xb589c7bc in _fini () from /lib/libselinux.so.1 #4 0xb7fe7fdf in ?? () from /lib/ld-linux.so.2 #5 0xb7e4d084 in exit () from /lib/tls/i686/cmov/libc.so.6 #6 0x08067929 in ruby_stop (ex=0) at eval.c:1652 #7 0x0806ce61 in ruby_run () at eval.c:1673 #8 0x08054faf in main (argc=-1208002968, argv=0xb7ff5948, envp=0x8166da8) at main.c:48 (gdb) As reported by Mario, it seems to be related with selinux. But on my system selinux is disabled : getenforce returns Disabled. Cheers. Chauk-Mean. From noreply at rubyforge.org Sat Sep 20 13:55:35 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 20 Sep 2008 13:55:35 -0400 (EDT) Subject: [wxruby-development] [ wxruby-Bugs-22041 ] tZTGPqqCE Message-ID: <20080920175535.E67D018585B1@rubyforge.org> Bugs item #22041, was opened at 2008-09-20 13:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=22041&group_id=35 Category: Incorrect or missing docs Group: v0.3 Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Alex Fenton (brokentoy) Summary: tZTGPqqCE Initial Comment: 9uOv2D izztyhckpitw, [url=http://ytecljcaayvv.com/]ytecljcaayvv[/url], [link=http://arukfqmvgsct.com/]arukfqmvgsct[/link], http://mcdjynhtqkln.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=22041&group_id=35 From mario at ruby-im.net Sat Sep 20 17:51:03 2008 From: mario at ruby-im.net (Mario Steele) Date: Sat, 20 Sep 2008 16:51:03 -0500 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: Yeah, I found that SELinux doesn't necessarily need to be enabled in order for it to throw the error. As to why it's crashing, your guess is as good as mine. On Sat, Sep 20, 2008 at 6:27 AM, Chauk-Mean P wrote: > Hi, > > >2008/9/7 Mario Steele : > >> Actually, I get the crash on exit with my app, and I think it's again > the > >> culprit of SELinux that is causing the problem, cause when I run the > core > >> dump through GDB, it gives SELinux as the culprit just before the > >> __kernel_vsyscall(). > > Here is the backtrace when I run the minimal sample from gdb : > > gdb --args ruby -Ilib samples/minimal/minimal.rb > GNU gdb 6.8-debian > Copyright (C) 2008 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later < > http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i486-linux-gnu"... > (gdb) r > Starting program: /opt/bin/ruby -Ilib samples/minimal/minimal.rb > [Thread debugging using libthread_db enabled] > Error while reading shared library symbols: > Cannot find new threads: generic error > Cannot find new threads: generic error > (gdb) c > Continuing. > Calling wxEntry, this=0x81fe848 > [New Thread 0xb7e1e8c0 (LWP 29321)] > OnExit... > ~wxRubyApp > returned from wxEntry... > === Starting App GC mark phase > === App has ended, skipping mark phase > survived gc > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb7e1e8c0 (LWP 29321)] > 0xb589af74 in ?? () from /lib/libselinux.so.1 > (gdb) whe > #0 0xb589af74 in ?? () from /lib/libselinux.so.1 > #1 0xb589464e in ?? () from /lib/libselinux.so.1 > #2 0xb588d100 in ?? () from /lib/libselinux.so.1 > #3 0xb589c7bc in _fini () from /lib/libselinux.so.1 > #4 0xb7fe7fdf in ?? () from /lib/ld-linux.so.2 > #5 0xb7e4d084 in exit () from /lib/tls/i686/cmov/libc.so.6 > #6 0x08067929 in ruby_stop (ex=0) at eval.c:1652 > #7 0x0806ce61 in ruby_run () at eval.c:1673 > #8 0x08054faf in main (argc=-1208002968, argv=0xb7ff5948, envp=0x8166da8) > at main.c:48 > (gdb) > > As reported by Mario, it seems to be related with selinux. > But on my system selinux is disabled : > getenforce returns > Disabled. > > Cheers. > > Chauk-Mean. > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > -- Mario Steele http://www.trilake.net http://www.ruby-im.net http://rubyforge.org/projects/wxruby/ http://rubyforge.org/projects/wxride/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From niklas.baumstark at googlemail.com Sun Sep 21 05:16:12 2008 From: niklas.baumstark at googlemail.com (Niklas Baumstark) Date: Sun, 21 Sep 2008 11:16:12 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> Message-ID: <20080921111612.31597bc8@niklaspc> Hello, just a guess: i had a similiar issue on my ubuntu hardy box with wxRuby 1.9.7 and solved it by compiling libselinux1 with DISABLE_SETRANS=y. maybe you should have a look at https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/237156 . Greetings, Niklas "Chauk-Mean P" wrote: > Hi, > > >2008/9/7 Mario Steele : > >> Actually, I get the crash on exit with my app, and I think it's again the > >> culprit of SELinux that is causing the problem, cause when I run the core > >> dump through GDB, it gives SELinux as the culprit just before the > >> __kernel_vsyscall(). > > Here is the backtrace when I run the minimal sample from gdb : > > gdb --args ruby -Ilib samples/minimal/minimal.rb > GNU gdb 6.8-debian > Copyright (C) 2008 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i486-linux-gnu"... > (gdb) r > Starting program: /opt/bin/ruby -Ilib samples/minimal/minimal.rb > [Thread debugging using libthread_db enabled] > Error while reading shared library symbols: > Cannot find new threads: generic error > Cannot find new threads: generic error > (gdb) c > Continuing. > Calling wxEntry, this=0x81fe848 > [New Thread 0xb7e1e8c0 (LWP 29321)] > OnExit... > ~wxRubyApp > returned from wxEntry... > === Starting App GC mark phase > === App has ended, skipping mark phase > survived gc > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb7e1e8c0 (LWP 29321)] > 0xb589af74 in ?? () from /lib/libselinux.so.1 > (gdb) whe > #0 0xb589af74 in ?? () from /lib/libselinux.so.1 > #1 0xb589464e in ?? () from /lib/libselinux.so.1 > #2 0xb588d100 in ?? () from /lib/libselinux.so.1 > #3 0xb589c7bc in _fini () from /lib/libselinux.so.1 > #4 0xb7fe7fdf in ?? () from /lib/ld-linux.so.2 > #5 0xb7e4d084 in exit () from /lib/tls/i686/cmov/libc.so.6 > #6 0x08067929 in ruby_stop (ex=0) at eval.c:1652 > #7 0x0806ce61 in ruby_run () at eval.c:1673 > #8 0x08054faf in main (argc=-1208002968, argv=0xb7ff5948, envp=0x8166da8) > at main.c:48 > (gdb) > > As reported by Mario, it seems to be related with selinux. > But on my system selinux is disabled : > getenforce returns > Disabled. > > Cheers. > > Chauk-Mean. > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From chauk.mean at gmail.com Sun Sep 21 12:32:32 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Sun, 21 Sep 2008 18:32:32 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: <20080921111612.31597bc8@niklaspc> References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> <20080921111612.31597bc8@niklaspc> Message-ID: Hi Niklas, Thanks a lot. This works also for me. 2008/9/21 Niklas Baumstark : > Hello, > > just a guess: i had a similiar issue on my ubuntu hardy box with wxRuby 1.9.7 and solved it by compiling libselinux1 with DISABLE_SETRANS=y. maybe you should have a look at https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/237156 . > It may be worth to indicate this workaround in the wxRuby wiki. Cheers. Chauk-Mean. From niklas.baumstark at googlemail.com Sun Sep 21 14:25:18 2008 From: niklas.baumstark at googlemail.com (Niklas Baumstark) Date: Sun, 21 Sep 2008 20:25:18 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C013EB.6060805@pressure.to> <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> <20080921111612.31597bc8@niklaspc> Message-ID: <20080921202518.14f142a8@niklaspc> Hello, "Chauk-Mean P" wrote: > Hi Niklas, > > Thanks a lot. This works also for me. you're welcome. > It may be worth to indicate this workaround in the wxRuby wiki. I'd like to, but at the moment i have no idea where to put it. should this go to the installation notes? Greetings, Niklas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From chauk.mean at gmail.com Mon Sep 22 04:40:05 2008 From: chauk.mean at gmail.com (Chauk-Mean P) Date: Mon, 22 Sep 2008 10:40:05 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: <20080921202518.14f142a8@niklaspc> References: <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> <20080921111612.31597bc8@niklaspc> <20080921202518.14f142a8@niklaspc> Message-ID: Hi Niklas, 2008/9/21 Niklas Baumstark : >> It may be worth to indicate this workaround in the wxRuby wiki. > > I'd like to, but at the moment i have no idea where to put it. should this go to the installation notes? This seems to be the appropriate place. I''ve just seen that you already updated the corresponding page :-) Cheers. Chauk-Mean. From niklas.baumstark at googlemail.com Mon Sep 22 07:30:38 2008 From: niklas.baumstark at googlemail.com (Niklas Baumstark) Date: Mon, 22 Sep 2008 13:30:38 +0200 Subject: [wxruby-development] Feedbacks on wxRuby 1.9.8 In-Reply-To: References: <48C1A3C6.80208@pressure.to> <48C29E0D.9020607@pressure.to> <20080921111612.31597bc8@niklaspc> <20080921202518.14f142a8@niklaspc> Message-ID: <20080922133038.5cbb42b9@niklaspc> Hello, "Chauk-Mean P" wrote: > Hi Niklas, > > 2008/9/21 Niklas Baumstark : > >> It may be worth to indicate this workaround in the wxRuby wiki. > > > > I'd like to, but at the moment i have no idea where to put it. should this go to the installation notes? > > This seems to be the appropriate place. > I''ve just seen that you already updated the corresponding page :-) > > Cheers. > > Chauk-Mean. Maybe anybody also experiencing this problem could add their system to the note? Don't know if this is an Ubuntu Hardy issue only. Greetings, Niklas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: