Are there any more information i can extract from the core enabling more debugging.gdb) backtrace #0 0xfeae7253 in syb_st_destroy () from /usr/local/lib/perl5/site_per +l/5.8.6/i86pc-solaris/auto/DBD/Sybase/Sybase.so #1 0x08183c80 in ?? () #2 0x08365b8c in ?? () #3 0x1d7d7640 in ?? () #4 0xfeaff840 in ?? () from /usr/local/lib/perl5/site_perl/5.8.6/i86p +c-solaris/auto/DBD/Sybase/Sybase.so #5 0xfead99ab in XS_DBD__Sybase__st_DESTROY () from /usr/local/lib/pe +rl5/site_perl/5.8.6/i86pc-solaris/auto/DBD/Sybase/Sybase.so #6 0x08183c8c in ?? () #7 0x00000004 in ?? () #8 0xfec40b5c in ?? () from /usr/local/lib/perl5/site_perl/5.8.6/i86p +c-solaris/auto/DBI/DBI.so #9 0x08183c80 in ?? () #10 0x08183cc0 in ?? () #11 0x00000000 in ?? () (gdb)
In reply to Re^2: Understanding the segmentation fault output generated using gdb
by Anonymous Monk
in thread Understanding the segmentation fault output generated using gdb
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |