SOS!

[Leon Pollak]

Sorry, I forgot to mention that after upgrade debugger did not start at 
all, just hanging.
I opened the console messages and saw that it is stuck at the line
source ..../printers/gdbinit 
When I removed this file, kdevelop started to run, but as I described 
previously...

--
Now, I decided to reinstall everything. I said "yum remove kdevelop" 
and "yum install kdevelop".

>From now on starting debug session brings:
Gdb crashed.
Because of that the debug session has to be ended.
Try to reproduce the crash with plain gdb and report a bug.
No need to say that plain gdb works fine...

Starting kdevelop from command line produces at the moment of pressing 
"debug" button:

execute composite (GDBDebugger::DebugJob(0x5282120, name = "ARM") )  
QObject::startTimer: QTimer cannot have a negative interval
QObject::startTimer: QTimer cannot have a negative interval

and the above error message (crash) appears. Pressing OK prints:

QObject::startTimer: QTimer cannot have a negative interval
QObject::startTimer: QTimer cannot have a negative interval
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x6c00660


Is there something I can do here?
-- 
Leon