Hi Dave,
> The stack trace will almost always tell you what went wrong.
> Not in much detail sometimes but usually enough to give you
> a hint what the problem was (or at least where it was).
$> gdb opera core
GNU gdb 4.18
[snip]
...
(gdb) where
#0 0x401983b7 in QFontDatabasePrivate::families ()
from /usr/lib/qt-2.0.1/lib/libqt.so.2
#1 0x4019d4de in QFontDatabase::families ()
from /usr/lib/qt-2.0.1/lib/libqt.so.2
#2 0x8143372 in FindToolbar::slotMatchWhole ()
#3 0x80d8836 in XtRemoveTimeOut ()
#4 0x404881eb in __libc_start_main (
main=0x8075ef0 <QApplication::commitData(QSessionManager &)+28356>,
argc=1, argv=0xbffffb84, init=0x806a45c <_init>, fini=0x82466a8 <_fini>,
rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffb7c)
at ../sysdeps/generic/libc-start.c:90
(gdb)
Hmmm.. libc-start.c line 90.
I'm running libc.so.5, Other than up/down grading I guess I can just
wait till they bring out the beta version. Well it was a bit of fun
anyway.
Pete
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
