KDE-Forum.org

I do not know if you have compiled Kopete yourself. If you did, you could run it with gdb.

Open a konsole, run
gdb kopete
then type
run
to start program
then try to make kopete go crazy.
When it is done go back to gdb, make Control-C
and type:
bt

Then you have a backtrace that you can send to KDE Bugs.
(You quit gdb with quit .)

If you have not compiled Kopete yourself, you probably have no bug symbols and therefore using gdb will not help.

Have a nice...

I for one am having this problem too.

Originally I thought it was old Kopete plugins interfering.

But it's quite frustrating, it's swapping out hard in an infinate loop / panic.

The only real solution I would see is settign a hard ulimit of 500meg ram useable.

But that's not very viable of solution, it's something that's in CVS

I'm running SuSE 8.2 with GCC 3.3 Alpha whatever the fuck it is,

I cvs'd as of saturday, and It happens on every 3 im's that it locks up,

Quite dramatic and quite hard to gdb, can't even get the log to save because when I reboot, it has to reboot hard.

I can ssh in barely to hit reboot, takes 4-5x to reboot and don't even think about doing gdb.

the load is over 15 when this happens, takes over a minute and a half just to login over lan.

So trust me when I say this, gdb ain't happening.

I've tried also saving the 'debug output' to no avail because of the reboot, fsck sets it to 0 size.

Unfortunatly not helpful.

Ideas?

Please have a look at this bug and see if it's the same.

http://bugs.kde.org/show_bug.cgi?id=63286

If it is the same please tag a 'me too' with kopete and kde versions onto the bugzilla entry.

We've been trying to track this one down but we're finding it hard to reproduce.