I'm getting a segfault right now trying to open the schema browser on a postgres connection:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a157c6 in QString::operator==(QString const&) const () from /usr/lib/libQtCore.so.4
(gdb) bt
#0  0x00007ffff7a157c6 in QString::operator==(QString const&) const () from /usr/lib/libQtCore.so.4
#1  0x0000000000458243 in toCache::updateObjects (this=<value optimized out>, owner=<value optimized out>, type=..., rows=<value optimized out>) at tocache.cpp:524
#2  0x000000000066fcea in toBrowserSchemaTableView::updateCache (this=<value optimized out>) at tobrowserschemawidget.cpp:98
#3  0x000000000070e930 in toBrowserSchemaTableView::qt_metacall (this=0x15ac390, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>)
    at moc_tobrowserschemawidget.cpp:74
#4  0x00007ffff7adae3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#5  0x0000000000707014 in toResultTableView::qt_metacall (this=0x15ac390, _c=QMetaObject::InvokeMetaMethod, _id=20721312, _a=0x7fffffffd070) at moc_toresulttableview.cpp:112
#6  0x000000000070e918 in toBrowserSchemaTableView::qt_metacall (this=0x13c2e98, _c=25189424, _id=20721312, _a=0x188f8c0) at moc_tobrowserschemawidget.cpp:69
#7  0x00007ffff7adae3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#8  0x00000000004cdd8f in toResultModel::cleanup (this=0x7fffe4000da0) at toresultmodel.cpp:163
#9  0x00000000004ce0e6 in toResultModel::readData (this=<value optimized out>) at toresultmodel.cpp:263
#10 0x00000000004ce42c in toResultModel::fetchMore (this=0x7fffe4000da0) at toresultmodel.cpp:782
#11 0x0000000000706d54 in toResultModel::qt_metacall (this=0x7fffe4000da0, _c=QMetaObject::InvokeMetaMethod, _id=20721312, _a=0x7fffffffd370) at moc_toresultmodel.cpp:100
#12 0x00007ffff7adae3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x00000000006fdb60 in toEventQuery::done (this=0x13c2e98, _t1=0x7fffe4008cb0) at moc_toeventquery.cpp:138
#14 0x00000000006fdda4 in toEventQuery::qt_metacall (this=0x7fffe4008cb0, _c=QMetaObject::InvokeMetaMethod, _id=20721312, _a=0x7fffe400ef30) at moc_toeventquery.cpp:103
#15 0x00007ffff7ad7d49 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00007ffff6e8122c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00007ffff6e876fb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00007ffff7ac806c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0x00007ffff7aca7e7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#20 0x00007ffff7af19d3 in ?? () from /usr/lib/libQtCore.so.4
#21 0x00007ffff22db8c2 in g_main_dispatch (context=0xee2520) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960
#22 IA__g_main_context_dispatch (context=0xee2520) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513
#23 0x00007ffff22df748 in g_main_context_iterate (context=0xee2520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591
#24 0x00007ffff22df8fc in IA__g_main_context_iteration (context=0xee2520, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654
#25 0x00007ffff7af1513 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x00007ffff6f3146e in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007ffff7ac6992 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007ffff7ac6d6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00007ffff7acaaab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#30 0x000000000043562c in main (argc=1, argv=<value optimized out>) at main.cpp:284


On Sat, Dec 18, 2010 at 1:40 PM, Tomas Straupis <tomasstraupis@gmail.com> wrote:
2010-12-12 Neulinger, Nathan:
> If significant additional use of the cache is introduced, I would like to see
> an easy to use button/menu-item (not buried) to clear/flush the cache -
> both for security/data purposes and for 'glitches' that are certain to occur.

 Could you clarify, are current changes "significant"?
 Is current menu option to re-read the cache sufficient?
 For security reasons, should the option be added to say prevent
userlist from being saved to disk (currently you can do that by
disabling storing cache contents on disk altogether)?

--
Tomas Straupis

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Tora-develop mailing list
Tora-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tora-develop



--
Open source monitoring done right: http://www.leemba.com