https://bugs.kde.org/show_bug.cgi?id=387232
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDSINFO
Resolution|--- |FIXED
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
#12 KDirWatchPrivate::entry (this=0x6, _path=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-kcoreaddons/work/kcoreaddons-5.38.0/src/lib/io/kdirwatch.cpp:597
#13 0x00007fd1d012294d in KDirWatch::contains (this=0x4f53570, _path=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-kcoreaddons/work/kcoreaddons-5.38.0/src/lib/io/kdirwatch.cpp:1967
#14 0x00007fd1caf06892 in KDevelop::ProjectWatcher::addDir (this=0x4f53570,
path=..., watchModes=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kdevelop/kf5-kdevelop-devel/work/kf5-kdevelop-5/kdevplatform/project/projectwatcher.cpp:39
Are you sure the dirwatch in your project watcher class is actually still
valid? This looks like a queued event triggers a call to ProjectWatcher::addDir
which then tries to access an already-deleted KDirWatch (note the this=0x6 of
the KDirWatchPrivate). I doubt this is a bug in KDirWatch, but rather your code
that is calling it is broken.
--
You are receiving this mail because:
You are watching all bug changes.
