wxruby development - Dec 2006 - [ wxruby-Bugs-7503 ] Segfaults on exception, related to sizer

Bugs item #7503, was opened at 2006-12-30 19:28
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=7503&group_id=35

Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Alex Fenton (brokentoy)
Assigned to: Alex Fenton (brokentoy)
Summary: Segfaults on exception, related to sizer

Initial Comment:
In applications which use sizers, a ruby exception being raised often causes the
application to segfault rather than end cleanly. This happens with many
different standard Ruby exception types: NoMethodError, ArgumentError etc.

This appears to be due to incorrect sequencing of sizer item destruction. An
example backtrace (OS X ppc):

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x0e40be00 in ?? ()
(gdb) whe
#0  0x0e40be00 in ?? ()
Cannot access memory at address 0xe40be00
Cannot access memory at address 0xe40be00
#1  0x032cb3d0 in wxSizerItem::~wxSizerItem() ()
#2  0x032cbd54 in wxSizer::~wxSizer() ()
#3  0x031aeec8 in
SwigDirector_wxStaticBoxSizer::~SwigDirector_wxStaticBoxSizer() ()
#4  0x0001d6f0 in rb_gc_call_finalizer_at_exit () at gc.c:1858
#5  0x000041d4 in ruby_finalize_1 () at eval.c:1418
#6  0x00004340 in ruby_cleanup (ex=1) at eval.c:1453
#7  0x000044b8 in ruby_stop (ex=6831776) at eval.c:1484
#8  0x00004544 in ruby_run () at eval.c:1505
#9  0x0000209c in main (argc=4, argv=0xbffff93c, envp=0x2) at main.c:46
#10 0x00001b5c in _start (argc=4, argv=0xbffff93c, envp=0xbffff950) at
/SourceCache/Csu/Csu-47/crt.c:267
#11 0x8fe1a31c in __dyld__dyld_start ()





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

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