-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Wednesday 24 March 2004 03:13, Jens Dagerbo wrote:
> Obviously, something changed in kdelibs, the question is, what...?

A few clues:

breaking in gdb gives me: 

(gdb) backtrace 
#0  0x411caa86 in QEventLoop::activateSocketNotifiers() () 
from /opt/qt-3.2.1/lib/libqt-mt.so.3
#1  0x411c996e in qt_wait_timer() () from /opt/qt-3.2.1/lib/libqt-mt.so.3
#2  0x41186fc2 in QEventLoop::processEvents(unsigned) () 
from /opt/qt-3.2.1/lib/libqt-mt.so.3
#3  0x411ee0e6 in QEventLoop::enterLoop() () 
from /opt/qt-3.2.1/lib/libqt-mt.so.3
#4  0x411edf88 in QEventLoop::exec() () from /opt/qt-3.2.1/lib/libqt-mt.so.3
#5  0x411db071 in QApplication::exec() () from /opt/qt-3.2.1/lib/libqt-mt.so.3
#6  0x08062550 in main (argc=1, argv=0xbffff494) at main.cpp:126
#7  0x41a7bb47 in __libc_start_main () from /lib/libc.so.6


I also noticed that you don't have to close the files to make the problem high 
cpu load go away, it's enough to switch to each of the files in "non-rapid 
fashion" (let each be visible for a few moments before switching to the 
next).


And.. it doesn't happen with the QEditor part, only with katepart.


jd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAYPEf6meJzsUuplQRArzLAKCROgdLW/zpLfpRV8CyX3nNepLScACgqC/K
+dL379nVxOinZ/d3bQhtoEc=
=aeji
-----END PGP SIGNATURE-----

_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel