KFileItem / KFileIconView bug?
sascha.cunz at tiscali.de
Wed May 25 22:49:55 BST 2005
in bugs.kde.org i found at least 3 bugs that crash in the destructor of
This destructor is a one-liner that (from my point of view) can just crash if
the KFileItem is destroyed before the KFileIconViewItem ( Or if the KFileItem
was never valid, which i doubt to be the case).
Looking at a Bugzilla query for "~KFileIconViewItem" in open and closed bugs
reveals that such behavior is there since before KDE 2.0 (Though the code
must have been changed for KDE3.0)
How likely is it that a KFileItem is destroyed unwanted or too early?
If I'm right in that, then shouldn't it possible to use a pointer that will
reset itself to NULL when the object it points to is deleted? Maybe we can
introduce some safety here for KDE4?
http://bugs.kde.org/show_bug.cgi?id=71121 (Closed by reporter)
http://bugs.kde.org/show_bug.cgi?id=60770 (Doubt that fix is related to
problem; fix seems to "avoid" problem)
Older (closed) bugs that also have backtraces showing the last known code
position to be ~KFileIconViewItem exist.
More information about the kde-core-devel