Bug 86451

I got this backtrace after trying to submit this bug report in konqueror

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1098326560 (LWP 19840)]
[KCrash handler]
#7  0x40805015 in KIconLoader::loadIcon (this=0x83cfeb0, _name=@0x84ad19c, 
    group=Toolbar, size=22, state=2, path_store=0x0, canReturnNull=false)
    at kiconloader.cpp:554
#8  0x408082a8 in KIconFactory::createPixmap (this=0x84ad190, mode_P=Disabled)
    at kiconloader.cpp:1181
#9  0x40c902f3 in QIconSetPrivate::icon (this=0x84ad570, iconSet=0xbfffe9d0, 
    size=Small, mode=Disabled, state=Off) at kernel/qiconset.cpp:195
#10 0x40c90a35 in QIconSet::pixmap (this=0xbfffe9d0, size=Small, 
    mode=Disabled, state=Off) at kernel/qiconset.cpp:520
#11 0x405b4cf8 in KToolBarButton::drawButton (this=0x84aceb0, 
    _painter=0x846fed8) at ktoolbarbutton.cpp:474
#12 0x40d607e7 in QButton::paintEvent (this=0x84aceb0)
    at widgets/qbutton.cpp:887
#13 0x40d03390 in QWidget::event (this=0x84aceb0, e=0xbfffed10)
    at kernel/qwidget.cpp:4774
#14 0x40c682eb in QApplication::internalNotify (this=0xbffff330, 
    receiver=0x84aceb0, e=0xbfffed10) at kernel/qapplication.cpp:2620
#15 0x40c67f1b in QApplication::notify (this=0xbffff330, receiver=0x84aceb0, 
    e=0xbfffed10) at kernel/qapplication.cpp:2508
#16 0x407a1d82 in KApplication::notify (this=0xbffff330, receiver=0x84aceb0, 
    event=0xbfffed10) at kapplication.cpp:495
#17 0x40bfe45d in QApplication::sendSpontaneousEvent (receiver=0x84aceb0, 
    event=0xbfffed10) at qapplication.h:494
#18 0x40bf98ec in QETWidget::translatePaintEvent (this=0x84aceb0, 
    event=0xbffff0b0) at kernel/qapplication_x11.cpp:5603
#19 0x40bf52df in QApplication::x11ProcessEvent (this=0xbffff330, 
    event=0xbffff0b0) at kernel/qapplication_x11.cpp:3456
#20 0x40c0f6d0 in QEventLoop::processEvents (this=0x8130c90, flags=4)
    at kernel/qeventloop_x11.cpp:192
#21 0x40c7c4b2 in QEventLoop::enterLoop (this=0x8130c90)
    at kernel/qeventloop.cpp:198
#22 0x40c7c3ce in QEventLoop::exec (this=0x8130c90)
    at kernel/qeventloop.cpp:145
#23 0x40c6846b in QApplication::exec (this=0xbffff330)
    at kernel/qapplication.cpp:2743
#24 0x418e1245 in kdemain (argc=2, argv=0x8078f40) at konq_main.cc:204
#25 0x41864999 in kdeinitmain (argc=2, argv=0x8078f40) at konqueror_dummy.cc:2
#26 0x0804e2d6 in launch (argc=2, _name=0x8078f64 "konqueror", 
    args=0x8078f77 "\001", cwd=0x0, envc=1, envs=0x8078f88 "", 
    reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8078f8c "kube.i-kubed.org;1091469376;116545;3166_TIME3187514") at kinit.cpp:599
#27 0x0804f5ef in handle_launcher_request (sock=8) at kinit.cpp:1163
#28 0x0804fcb8 in handle_requests (waitForPid=0) at kinit.cpp:1364
#29 0x08051194 in main (argc=3, argv=0xbffff994, envp=0xbffff9a4)
    at kinit.cpp:1817

They look like they're pretty similar.
Also sometimes after crashes drkonqui doesn't start.

and iirc these frequent crashes started after a problem I had with drkonqui where it didn't show up on screen but it was in the process list. And it caused any konq windows which had started up in file manager (but not broswer) mode to freeze. 
Oh and kdelibs, arts, and kdebase were built with gcc 3.3.3 but some of the other parts of kde were built with 3.4.1. Don't know if that helps any since the core was built with the same compiler, but what do i know :)

whoops. nearly forgot. To reproduce. Go to Help > Report Bug...
File a dummy bug report or something and then hit submit. Konqueror should then crash and DrKonqui may or may not start up. I have kde compiled with --enable-debug=full

Please do -NOT-  mix gcc-3.4 and 3.3.x, they are NOT compatible.

*** This bug has been marked as a duplicate of 68528 ***

If you could reproduce this from command-line, within valgrind, that would be exceptionally helpful. This family of bugs is a toughy. 

i can try but how'd I do that?
valgrind konqueror?

gone once i built kdebase and kdelibs w/ gcc 3.4