> No it is definitely not! It may be possible that there's a > few more places in > kdevplatform/kdevelop where this problem appears. Thanks for > spotting this. May be one of the reasons kdevelop only runs in debug mode? Sounds like someone needs to review the Q_ASSERT usage in that area. Kris Wong