Re: segfault on exit?

[Daniel Kasak <dkasak nusconsulting com au>]

muppet wrote:

> On Oct 26, 2004, at 1:52 AM, Daniel Kasak wrote:
>
> > to the app's menu's 'destroy' signal.
> > Is this something to worry about or not? Is there something I'm 
> > supposed to do other than 'exit'?
>
>
> using exit() shouldn't be a problem.
>
> a stack trace would help.  you can get one from a core file.
>
>
>   $ ulimit -c unlimited   # drop a core file on segfaults
>   $ perl yourscript.pl   # run it to make it segfault
>   $ gdb perl corefile
>   (gdb) backtrace
>   [send this text]

(gdb) backtrace
#0  0x486ce951 in g_signal_has_handler_pending () from 
/usr/lib/libgobject-2.0.so.0
#1  0x486ef0c4 in g_param_spec_types () from /usr/lib/libgobject-2.0.so.0
#2  0x2000000b in ?? ()
#3  0x00000000 in ?? ()
#4  0x00000000 in ?? ()
#5  0x0815c198 in ?? ()
#6  0x00000008 in ?? ()
#7  0x0815c180 in ?? ()
#8  0xbfffed73 in ?? ()
#9  0x6d6d6f63 in ?? ()
#10 0x3a3a6e6f in ?? ()
#11 0xbfffec00 in ?? ()
#12 0x080be4bd in Perl_hv_fetch ()
#13 0x081580a8 in ?? ()
#14 0xbfffed80 in ?? ()
#15 0xbfffece0 in ?? ()
#16 0x0000000b in ?? ()        
#17 0x481ea881 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
Previous frame inner to this frame (corrupt stack?)
(gdb)

Is this all you need? I compile everything with -O3 here, and I've read 
that this makes debugging harder. I can recompile with -O2 if necessary 
- I have no idea what the above is talking about, but there are a lot of 
?? () ... maybe this is the reason?

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak nusconsulting com au
website: http://www.nusconsulting.com.au

Title: CanIt Vote for ID 121903

---

The following links have been inserted by the NUS Consulting internal spam filter and are for NUS Consulting staff only
Spam
Not spam
Forget previous vote