OLDER NEWS
106283
PIE client programs are loaded at address 0
105831
Assertion ‘vgPlain_defined_init_shadow_page()’ failed.
105039
long run-times probably due to memory manager
104797
valgrind needs to be aware of BLKGETSIZE64
103594
unhandled instruction: FICOM
103320
Valgrind 2.4.0 fails to compile with gcc 3.4.3 and -O0
103168
potentially memory leak in coregrind/ume.c
102039
bad permissions for mapped region at address 0xB7C73680
101881
weird assertion problem
101543
Support fadvise64 syscalls
75247
x86_64/amd64 support (the biggest "bug" we have ever fixed)
(3.0RC1: 27 July
05, vex r1303, valgrind r4283).
(3.0.0:
3 August 05, vex r1313, valgrind r4316).
Stable release 2.4.1 (1 August 2005)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(The notes for this release have been lost.
Sorry!
It would have
contained various bug fixes but no new features.)
Stable release 2.4.0 (March 2005) -- CHANGES RELATIVE TO 2.2.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.4.0 brings many significant changes and bug fixes.
The most
significant user-visible change is that we no longer supply our own
pthread implementation.
Instead, Valgrind is finally capable of
running the native thread library, either LinuxThreads or NPTL.
This means our libpthread has gone, along with the bugs associated
with it.
Valgrind now supports the kernel’s threading syscalls, and
lets you use your standard system libpthread.
As a result:
* There are many fewer system dependencies and strange library-related
bugs.
There is a small performance improvement, and a large
stability improvement.
* On the downside, Valgrind can no longer report misuses of the POSIX
PThreads API.
It also means that Helgrind currently does not work.
We hope to fix these problems in a future release.
Note that running the native thread libraries does not mean Valgrind
is able to provide genuine concurrent execution on SMPs.
We still
impose the restriction that only one thread is running at any given
time.
There are many other significant changes too:
* Memcheck is (once again) the default tool.
* The default stack backtrace is now 12 call frames, rather than 4.
56
Содержание 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 ...