| Summary: | Incorrect English in message | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Blake McBride <blake1024> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | blake1024, philippe.waroquiers |
| Priority: | NOR | ||
| Version First Reported In: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Blake McBride
2017-07-17 17:53:34 UTC
I am not sure to understand what is really wrong in this message, but it is like that since at least 2009 and nobody complained up to now about a difficulty to understand it. As tests are depending on this output, and possibly some users have scripts checking for this string, it looks better to not improve this message, as the cost/benefit seems not that good The message as it stands is really what I intended. If all heap blocks are freed then it isn't possible to have any leaks, since there are no blocks to leak. Hence the wording. |