search for: wxtoplevelwindowbase

Displaying 3 results from an estimated 3 matches for "wxtoplevelwindowbase".

2007 Jan 25
0
[ wxruby-Bugs-8130 ] Crash-on-exit when dialogs have been used
...been shown with show_modal, the following crash occurs on application exit Program received signal EXC_BAD_ACCESS, Could not access memory. 0xf4000104 in ?? () (gdb) whe #0 0xf4000104 in ?? () Cannot access memory at address 0xf4000104 Cannot access memory at address 0xf4000104 #1 0x0335d888 in wxTopLevelWindowBase::~wxTopLevelWindowBase() () #2 0x0335be10 in wxTopLevelWindowMac::~wxTopLevelWindowMac() () #3 0x0335e478 in wxDialog::~wxDialog() () #4 0x030fccfc in SwigDirector_wxMessageDialog::~SwigDirector_wxMessageDialog() () #5 0x0001d6f0 in rb_gc_call_finalizer_at_exit () at gc.c:1858 #6 0x000041d4 in...
2007 Jan 26
0
[ wxruby-Bugs-8179 ] Segfaults when Kernel#exit is called
...'s initializer that ensures main_loop is ended correctly. Backtrace is: Program received signal EXC_BAD_ACCESS, Could not access memory. 0xf4000104 in ?? () (gdb) whe #0 0xf4000104 in ?? () Cannot access memory at address 0xf4000104 Cannot access memory at address 0xf4000104 #1 0x0335d888 in wxTopLevelWindowBase::~wxTopLevelWindowBase() () #2 0x0335be10 in wxTopLevelWindowMac::~wxTopLevelWindowMac() () #3 0x0335e478 in wxDialog::~wxDialog() () #4 0x030fccfc in SwigDirector_wxMessageDialog::~SwigDirector_wxMessageDialog() () #5 0x0001d6f0 in rb_gc_call_finalizer_at_exit () at gc.c:1858 #6 0x000041d4 in...
2007 Mar 15
6
Patch to 0.0.39
Hi I''m developing software using wxruby2. At first I tried to use wxruby 0.6 but I couldn''t live without some of those new funky features :) So, instead of writing my own code, I got a bit sidetracked and wrote http://rubyforge.org/tracker/index.php?func=detail&aid=9297&group_id=35&atid=220 instead. Seeing as this is my first foray in to the innards of wxruby2, I