Version: (using KDE KDE 3.3.0) Installed from: Debian testing/unstable Packages OS: Linux Crash happened very randomly, for no apparent reason. Below is the console output. -brett brett@chitwan:~/pyode_cvs$ kate& [1] 6107 brett@chitwan:~/pyode_cvs$ Creating link /home/brett/.kde/socket-chitwan. Created link from "/home/brett/.kde/socket-chitwan" to "/tmp/ksocket-brett" QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used Creating link /home/brett/.kde/tmp-chitwan. Created link from "/home/brett/.kde/tmp-chitwan" to "/tmp/kde-brett" QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used kbuildsycoca running... Creating link /home/brett/.kde/cache-chitwan. Created link from "/home/brett/.kde/cache-chitwan" to "/var/tmp/kdecache-brett" kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined mimetype/servicetype 'application/binary-certificate' kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-fortran' kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/servicetype 'KNotify' kate: WARNING: Can't open /home/brett/.kde/share/apps/konqueror/bookmarks.xml kate: WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance ) kate: WARNING: KServiceType::offers : servicetype ThumbCreator not found kate: WARNING: KServiceType::offers : servicetype ThumbCreator not found kate: WARNING: KServiceType::offers : servicetype ThumbCreator not found kate: WARNING: KServiceType::offers : servicetype ThumbCreator not found kate: WARNING: KServiceType::offers : servicetype ThumbCreator not found ASSERT: "thisRange.virtualLine == virtualCursor.line()" in ../../../kate/part/kateviewinternal.cpp (1474)KCrash: Application 'kate' crashing... Unable to start Dr. Konqi Mutex destroy failure: Device or resource busy ICE default IO error handler doing an exit(), pid = 6118, errno = 0
That's interesting, I didn't know there was a way of building Qt that changes Q_ASSERT into a fatal condition... Anyway, roughly how often does this happen? (crashes per hour of usage). Thanks, Hamish.
--- Hamish Rodda <rodda@kde.org> wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=90666 > > > > > ------- Additional Comments From rodda kde org 2004-10-03 15:31 ------- > That's interesting, I didn't know there was a way of building Qt that changes Q_ASSERT into a > fatal condition... > > Anyway, roughly how often does this happen? (crashes per hour of usage). > > Thanks, Hamish. > It crashed after about 10 minutes of use, i have not used Kate since then on that machine, if i get around to doing more testing i'll let you know. -brett __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
On Sunday 03 October 2004 15:31, Hamish Rodda wrote: > That's interesting, I didn't know there was a way of building Qt that > changes Q_ASSERT into a fatal condition... The Q_ASSERT calls are very annoying for anyone trying to use the stderr output, since in opposition to kdDebug statements there is no way to supress them. One of them, related to dynamic word wrap, will very often output screenfulls of lines. What is the reason for using them in favour of a condition?
I use them simply because they shouldn't happen, and if they do, it's a bug. I don't remember this assert being a problem in the past. At the moment I'm not running KDE from cvs, so it's a bit hard for me to debug this - are you hitting the same assert, Anders?
I see the messages on stderr, but i never saw that particular one. anders@pluto anders $ grep ASSERT .xsession-errors |wc -l 5165 anders@pluto anders $ grep ASSERT .xsession-errors|grep virtualLine |wc -l 0 anders@pluto anders $ ( the 5165 ASSERTS from my ~2hr session are all this one: ASSERT: "!m_doc->wrapCursor()" in /home/anders/src/kde/kdelibs/kate/part/katerenderer.cpp (632) )
does not happen for CVS or kde 3.4 the other ASSERT has been both commented out and the reason for the triggering was fixed, IMHO