NEWS
but are directly pointed to by a start-pointer, were previously
marked as "still reachable".
They are now correctly marked as
"possibly lost".
- The default value for the --leak-resolution option has been
changed from "low" to "high".
In general, this means that more
leak reports will be produced, but each leak report will describe
fewer leaked blocks.
- With --leak-check=full, "definitely lost" and "possibly lost"
leaks are now considered as proper errors, ie. they are counted
for the "ERROR SUMMARY" and affect the behaviour of
--error-exitcode.
These leaks are not counted as errors if
--leak-check=summary is specified, however.
- Documentation for the leak checker has been improved.
* Various aspects of Valgrind’s text output have changed.
- Valgrind’s start-up message has changed.
It is shorter but also
includes the command being run, which makes it easier to use
--trace-children=yes.
An example:
- Valgrind’s shut-down messages have also changed.
This is most
noticeable with Memcheck, where the leak summary now occurs before
the error summary.
This change was necessary to allow leaks to be
counted as proper errors (see the description of the leak checker
changes above for more details).
This was also necessary to fix a
longstanding bug in which uses of suppressions against leaks were
not "counted", leading to difficulties in maintaining suppression
files (see https://bugs.kde.org/show_bug.cgi?id=186790).
- Behavior of -v has changed.
In previous versions, -v printed out
a mixture of marginally-user-useful information, and tool/core
statistics.
The statistics printing has now been moved to its own
flag, --stats=yes.
This means -v is less verbose and more likely
to convey useful end-user information.
- The format of some (non-XML) stack trace entries has changed a
little.
Previously there were six possible forms:
0x80483BF: really (a.c:20)
0x80483BF: really (in /foo/a.out)
0x80483BF: really
0x80483BF: (within /foo/a.out)
0x80483BF: ??? (a.c:20)
0x80483BF: ???
The third and fourth of these forms have been made more consistent
with the others.
The six possible forms are now:
0x80483BF: really (a.c:20)
0x80483BF: really (in /foo/a.out)
23
Содержание BBV
Страница 176: ...Valgrind FAQ Release 3 8 0 10 August 2012 Copyright 2000 2012 Valgrind Developers Email valgrind valgrind org ...
Страница 177: ...Valgrind FAQ Table of Contents Valgrind Frequently Asked Questions 1 ii ...
Страница 302: ...README mips based on newer GCC versions if possible 95 ...
Страница 303: ...GNU Licenses ...
Страница 304: ...GNU Licenses Table of Contents 1 The GNU General Public License 1 2 The GNU Free Documentation License 8 ii ...