https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #25 from Matthew Woehlke <[email protected]> --- > The cache gets corrupted - this is the root cause and should certainly be > fixed. Okay, while I grant that you probably know more about KDevelop's innards than I do, I remain skeptical of this claim. Again, I note that the crash occurs on the first execution within a pristine environment. If the *root* problem is cache corruption, that implies that something produces a bad result, writes it to disk, *reads it back* in the same instance, and causes heap corruption as a result, yes? > Valgrind is not the only tool ... Yes, I know, but it has the significant advantage of not needing to recompile the application being tested. (Or its dependent libraries, which IIUC may be needed for *san tools. And, especially if the problem relates to a Fedora patch, getting a build that actually has the problem may be challenging. That's not to say I won't possibly try that eventually, but not until I'm confident that valgrind can't help.) -- You are receiving this mail because: You are watching all bug changes.
