Bug#29808: I had this too

[Troy Corbin Jr.]

My KDevelop 2.0 ( Which came with KDE2.2 ) choked on me while I was scrolling 
a document. It did not create a KCrash dialog. Attempting to run it again 
brought up the splash screen, but the process dies a few seconds later. 
Again, no KCrash.

When I ran it from the command line, I recieved these messages:
 
DocViewMan::installBMPopup
QObject::connect: Incompatible sender/receiver arguments
        QSignal::x(int) --> CKDevelop::slotHelpTipOfDay(bool)

A KCrash dialog appeared this time. Here are it's contents:

[New Thread 1024 (LWP 18197)]
0x4138b5a9 in __wait4 () from /lib/libc.so.6
#0  0x4138b5a9 in __wait4 () from /lib/libc.so.6
#1  0x413f5824 in __DTOR_END__ () from /lib/libc.so.6
#2  0x409c253d in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3
#3  <signal handler called>
#4  0x8453520 in ?? ()
#5  0x40862c6f in KDockTabCtl::page () from /usr/lib/libkdeui.so.3
#6  0x408716ea in KDockManager::readConfig () from /usr/lib/libkdeui.so.3
#7  0x40866996 in KDockMainWindow::readDockConfig ()
   from /usr/lib/libkdeui.so.3
#8  0x80df9c7 in CKDevelop::CKDevelop ()
#9  0x80eda77 in main ()
#10 0x412f1b65 in __libc_start_main (main=0x80ecce8 <main>, argc=1,
    ubp_av=0xbffffa34, init=0x8061e40 <_init>, fini=0x820a1f4 <_fini>,
    rtld_fini=0x4000df24 <_dl_fini>, stack_end=0xbffffa2c)
    at ../sysdeps/generic/libc-start.c:111

Seeing #6-7, I removed my kdeveloprc file and now it is working again! I 
guess the config got bungled during the first crash. Here is a copy of my old 
config file so you can find the bad data. Good luck!

Config file that kept it from working:
http://fly.hiwaay.net/~corbin/kdeveloprc.old

-- 
Troy Corbin Jr.
tcorbin at users.sourceforge.net
http://knights.sourceforge.net

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«