Summary: | Callgrind does not distinguish between parent and child | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Christoph Bartoschek <bartoschek> |
Component: | callgrind | Assignee: | Josef Weidendorfer <josef.weidendorfer> |
Status: | ASSIGNED --- | ||
Severity: | normal | CC: | njn |
Priority: | NOR | ||
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christoph Bartoschek
2006-09-19 10:54:04 UTC
Ups. The bug is not a crash. In valgrind 3.2 this lead to a crash. But with valgrind 3.2.1 there is only the buggy behaviour. I can confirm this. It happens because some file names are prepared at startup which contain the PID, and there is no hook in callgrind for fork. As a patch probably will not be small and needs testing, there was no need to hurry to put it into 3.2.1. This is very similar to bug 162848. This is very similar to bug 162848. |