Bug 157154 - documentation (leak-resolution doc speaks about num-callers def=4) + what is a loss record
Summary: documentation (leak-resolution doc speaks about num-callers def=4) + what is ...
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.3.0
Platform: Compiled Sources Linux
: NOR minor
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-04 15:20 UTC by philippe.waroquiers
Modified: 2009-03-10 22:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description philippe.waroquiers 2008-02-04 15:20:50 UTC
two points about the documentation:

**** In the documentation of memcheck (section 4.2 paragraph explaining leak-
resolution), the default value for num-callers is listed as 4, while the
default value is documented as 12 (and is 12 in the code).

**** The leak error messages of memcheck contain an indication of 
"loss record xxx of xxxxx".
I have searched for the documentation of what this means, but could not find
anything explaining these.
It looks to me that these are "internal" numbers used to identify
stack traces considered unique by --leak-resolution but I am not sure of this.
It is unclear to me what these numbers can be used for.
If there is some semantic/usage for these loss record numbers, it would
be good to have some explanation about the usefulness of these otherwise
the doc could tell that these are not that useful.
Comment 1 Nicholas Nethercote 2009-03-10 22:45:28 UTC
Fixed on the trunk in r9341.  Will be in the 3.5.0 release.  Thanks for the report.

(Regarding the loss record numbers:  you are correct.  The order isn't really significant.  If you use --show-reachable they'll be in order from 1 to N, which makes things clearer.)