Summary: | KCachegrind crashes while try to show <cycle> function | ||
---|---|---|---|
Product: | [Developer tools] kcachegrind | Reporter: | Artyom Petrenkov <static.lab> |
Component: | general | Assignee: | Josef Weidendorfer <josef.weidendorfer> |
Status: | RESOLVED FIXED | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 0.7.4kde | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kcachegrind/689893989f783b7619695a37a7a7331202179269 | Version Fixed In: | 4.12.3 |
Sentry Crash Report: |
Description
Artyom Petrenkov
2014-02-04 07:00:50 UTC
Git commit 689893989f783b7619695a37a7a7331202179269 by Josef Weidendorfer. Committed on 06/01/2014 at 02:06. Pushed by weidendo into branch 'KDE/4.12'. Fix: Do not crash on functions with call count 0. Cherry-picked from master. Call count 0 may exist with Callgrind when measuring starts after the function was called but when the function is still active, ie. not returned yet. For "cost per call", it makes sense to show the full cost while the function was active. M +8 -0 libcore/costitem.cpp http://commits.kde.org/kcachegrind/689893989f783b7619695a37a7a7331202179269 Thanks for the report. There was a fix for some bug introduced with a recently added feature that did not make it into 4.12 branch. |