wxruby development - Jan 2007 - [ wxruby-Bugs-8179 ] Segfaults when Kernel#exit is called

Bugs item #8179, was opened at 2007-01-26 18:03
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=8179&group_id=35

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Alex Fenton (brokentoy)
Assigned to: Nobody (None)
Summary: Segfaults when Kernel#exit is called

Initial Comment:
If there are multiple windows or dialogs to be cleaned up, then calling
Ruby''s exit command can cause segfaults. This is because Wx''s
clean-up code for top-level windows references the App instance, which has
already been destroyed by Ruby''s GC

Poss solution - add an at_exit block to App''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 ruby_finalize_1 () at eval.c:1418
#7  0x00004340 in ruby_cleanup (ex=0) at eval.c:1453
#8  0x000044b8 in ruby_stop (ex=71295648) at eval.c:1484
#9  0x00004544 in ruby_run () at eval.c:1505

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=8179&group_id=35