KDevelop 2.0 crashed when error message is clicked
Julian Rockey
linux at jrockey.com
Mon Aug 20 07:19:39 BST 2001
re crash..
> #4 0x806d233 in DocViewMan::doSwitchToFile ()
> #5 0x809d90f in CKDevelop::switchToFile ()
> #6 0x8092fd8 in CKDevelop::slotSwitchToFile ()
The only place I can see a crash could happen is at
QextMdiChildView* pMDICover = (QextMdiChildView*)
pEditWidget->parentWidget();
pMDICover->activate();
If the edit widget has no parent, crash. Of course, this shouldn't happen.
When edit widgets are created they are always assigned a parent in
DocViewMan::addQExtMDIFrame. But maybe it is somehow. I've had situations in
KDevelop 2.0 where the edit windows have been all over the place, especially
after restarting after a previous crash.
Perhaps an assert or other test at this point would be a good idea, to catch
it if it happens?
-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«
More information about the KDevelop
mailing list