njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 1 | |
njn | 254dafe | 2009-02-09 03:25:04 +0000 | [diff] [blame] | 2 | Release 3.5.0 (???) |
| 3 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
njn | 8df80b2 | 2009-03-02 05:11:06 +0000 | [diff] [blame] | 4 | * A new Memcheck client request VALGRIND_COUNT_LEAK_BLOCKS has been added. |
| 5 | It is similar to VALGRIND_COUNT_LEAKS but counts blocks instead of bytes. |
| 6 | [XXX: consider adding VALGRIND_COUNT_LEAK_BYTES as a synonym and |
| 7 | deprecating VALGRIND_COUNT_LEAKS, which wasn't a good name to begin with] |
| 8 | |
njn | 8225cc0 | 2009-03-09 22:52:24 +0000 | [diff] [blame] | 9 | * Memcheck's leak checker has been improved. |
| 10 | - The results for --leak-check=summary now match the summary results for |
| 11 | --leak-check=full. Previously they could differ because |
| 12 | --leak-check=summary counted "indirectly lost" blocks and "suppressed" |
| 13 | blocks as "definitely lost". |
| 14 | - Blocks that are only reachable via at least one interior-pointer, but |
| 15 | are directly pointed to by a start-pointer, were previously marked as |
| 16 | "still reachable". They are now correctly marked as "possibly lost". |
| 17 | |
njn | 5e40aba | 2009-03-16 22:11:31 +0000 | [diff] [blame] | 18 | * The format of some (non-XML) stack trace entries has changed a little. |
| 19 | Previously there were six possible forms: |
| 20 | |
| 21 | 0x80483BF: really (a.c:20) |
| 22 | 0x80483BF: really (in /foo/a.out) |
| 23 | 0x80483BF: really |
| 24 | 0x80483BF: (within /foo/a.out) |
| 25 | 0x80483BF: ??? (a.c:20) |
| 26 | 0x80483BF: ??? |
| 27 | |
| 28 | The third and fourth of these forms have been made more consistent with |
| 29 | the others. The six possible forms are now: |
| 30 | |
| 31 | 0x80483BF: really (a.c:20) |
| 32 | 0x80483BF: really (in /foo/a.out) |
| 33 | 0x80483BF: really (in ???) |
| 34 | 0x80483BF: ??? (in /foo/a.out) |
| 35 | 0x80483BF: ??? (a.c:20) |
| 36 | 0x80483BF: ??? |
| 37 | |
| 38 | Stack traces produced when --xml=yes is specified are different and |
| 39 | unchanged. |
| 40 | |
njn | ace90d8 | 2009-04-27 01:27:58 +0000 | [diff] [blame^] | 41 | * The graphs drawn by Massif's ms_print program have changed slightly: |
| 42 | - The half-height chars '.' and ',' are no longer drawn, because they are |
| 43 | confusing. The --y option can be used if the default y-resolution is |
| 44 | not high enough. |
| 45 | - Horizontal lines are now drawn after the top of a snapshot if there is a |
| 46 | gap until the next snapshot. This makes it clear that the memory |
| 47 | usage has not dropped to zero between snapshots. |
| 48 | |
njn | 6bf365c | 2009-02-11 00:35:45 +0000 | [diff] [blame] | 49 | * The location of some install files has changed. This should not affect |
| 50 | most users. Those who might be affected: |
njn | 6bf365c | 2009-02-11 00:35:45 +0000 | [diff] [blame] | 51 | - For people who use Valgrind with MPI programs, the installed |
| 52 | libmpiwrap.so library has moved from $(INSTALL)/<platform>/libmpiwrap.so |
| 53 | to $(INSTALL)/libmpiwrap-<platform>.so. |
njn | 6bf365c | 2009-02-11 00:35:45 +0000 | [diff] [blame] | 54 | - For people who distribute standalone Valgrind tools, the installed |
| 55 | libraries such as $(INSTALL)/<platform>/libcoregrind.a have moved to |
| 56 | $(INSTALL)/libcoregrind-<platform>.a. |
| 57 | |
| 58 | These changes were made to simplify the build system. |
| 59 | |
njn | 254dafe | 2009-02-09 03:25:04 +0000 | [diff] [blame] | 60 | * Previously, all the distributed suppression (*.supp) files were installed. |
| 61 | Now, only default.supp is installed. This should not affect users as the |
| 62 | other installed suppression files were not read. |
| 63 | |
bart | 076d2b5 | 2009-03-22 10:14:39 +0000 | [diff] [blame] | 64 | n-i-bz DRD - race conditions between pthread_barrier_wait() and |
| 65 | pthread_barrier_destroy() calls are now reported. |
| 66 | n-i-bz DRD - added "first observed at" information in error |
| 67 | messages related to synchronization objects. |
| 68 | n-i-bz DRD - added new client request, VG_USERREQ__DRD_CLEAN_MEMORY. |
| 69 | 187048 DRD - the mutex attribute PTHREAD_PROCESS_SHARED is now |
| 70 | interpreted correctly. |
bart | 56174ad | 2009-04-05 11:01:19 +0000 | [diff] [blame] | 71 | 188046 Removed a bashism from the configure script. |
bart | cd99d94 | 2009-04-25 16:25:45 +0000 | [diff] [blame] | 72 | 189763 DRD - pthread_create@GLIBC_2.0() no longer triggers an assertion |
| 73 | failure. |
bart | 076d2b5 | 2009-03-22 10:14:39 +0000 | [diff] [blame] | 74 | |
njn | 254dafe | 2009-02-09 03:25:04 +0000 | [diff] [blame] | 75 | |
| 76 | |
njn | ad91a75 | 2009-03-13 19:55:36 +0000 | [diff] [blame] | 77 | Release 3.4.1 (28 February 2009) |
| 78 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 79 | 3.4.1 is a bug-fix release that fixes some regressions and assertion |
| 80 | failures in debug info reading in 3.4.0, most notably incorrect stack |
| 81 | traces on amd64-linux on older (glibc-2.3 based) systems. Various |
| 82 | other debug info problems are also fixed. A number of bugs in the |
| 83 | exp-ptrcheck tool introduced in 3.4.0 have been fixed. |
| 84 | |
| 85 | In view of the fact that 3.4.0 contains user-visible regressions |
| 86 | relative to 3.3.x, upgrading to 3.4.1 is recommended. Packagers are |
| 87 | encouraged to ship 3.4.1 in preference to 3.4.0. |
| 88 | |
| 89 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 90 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 91 | bugzilla entry. We encourage you to file bugs in bugzilla |
| 92 | (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than mailing the |
| 93 | developers (or mailing lists) directly -- bugs that are not entered |
| 94 | into bugzilla tend to get forgotten about or ignored. |
| 95 | |
| 96 | n-i-bz Fix various bugs reading icc-11 generated debug info |
| 97 | n-i-bz Fix various bugs reading gcc-4.4 generated debug info |
| 98 | n-i-bz Preliminary support for glibc-2.10 / Fedora 11 |
| 99 | n-i-bz Cachegrind and Callgrind: handle non-power-of-two cache sizes, |
| 100 | so as to support (eg) 24k Atom D1 and Core2 with 3/6/12MB L2. |
| 101 | 179618 exp-ptrcheck crashed / exit prematurely |
| 102 | 179624 helgrind: false positive races with pthread_create and |
| 103 | recv/open/close/read |
| 104 | 134207 pkg-config output contains @VG_PLATFORM@ |
| 105 | 176926 floating point exception at valgrind startup with PPC 440EPX |
| 106 | 181594 Bogus warning for empty text segment |
| 107 | 173751 amd64->IR: 0x48 0xF 0x6F 0x45 (even more redundant rex prefixes) |
| 108 | 181707 Dwarf3 doesn't require enumerations to have name |
| 109 | 185038 exp-ptrcheck: "unhandled syscall: 285" (fallocate) on x86_64 |
| 110 | 185050 exp-ptrcheck: sg_main.c:727 (add_block_to_GlobalTree): |
| 111 | Assertion '!already_present' failed. |
| 112 | 185359 exp-ptrcheck unhandled syscall getresuid() |
| 113 | |
| 114 | (3.4.1.RC1: 24 Feb 2008, vex r1884, valgrind r9253). |
| 115 | (3.4.1: 28 Feb 2008, vex r1884, valgrind r9293). |
| 116 | |
| 117 | |
| 118 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 119 | Release 3.4.0 (2 January 2009) |
| 120 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 121 | 3.4.0 is a feature release with many significant improvements and the |
| 122 | usual collection of bug fixes. This release supports X86/Linux, |
| 123 | AMD64/Linux, PPC32/Linux and PPC64/Linux. Support for recent distros |
| 124 | (using gcc 4.4, glibc 2.8 and 2.9) has been added. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 125 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 126 | 3.4.0 brings some significant tool improvements. Memcheck can now |
| 127 | report the origin of uninitialised values, the thread checkers |
| 128 | Helgrind and DRD are much improved, and we have a new experimental |
| 129 | tool, exp-Ptrcheck, which is able to detect overruns of stack and |
| 130 | global arrays. In detail: |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 131 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 132 | * Memcheck is now able to track the origin of uninitialised values. |
| 133 | When it reports an uninitialised value error, it will try to show |
| 134 | the origin of the value, as either a heap or stack allocation. |
| 135 | Origin tracking is expensive and so is not enabled by default. To |
| 136 | use it, specify --track-origins=yes. Memcheck's speed will be |
| 137 | essentially halved, and memory usage will be significantly |
| 138 | increased. Nevertheless it can drastically reduce the effort |
| 139 | required to identify the root cause of uninitialised value errors, |
| 140 | and so is often a programmer productivity win, despite running more |
| 141 | slowly. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 142 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 143 | * A version (1.4.0) of the Valkyrie GUI, that works with Memcheck in |
sewardj | b8b1664 | 2009-01-02 23:21:54 +0000 | [diff] [blame] | 144 | 3.4.0, will be released shortly. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 145 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 146 | * Helgrind's race detection algorithm has been completely redesigned |
| 147 | and reimplemented, to address usability and scalability concerns: |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 148 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 149 | - The new algorithm has a lower false-error rate: it is much less |
| 150 | likely to report races that do not really exist. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 151 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 152 | - Helgrind will display full call stacks for both accesses involved |
sewardj | f1fa5ed | 2008-12-23 17:04:52 +0000 | [diff] [blame] | 153 | in a race. This makes it easier to identify the root causes of |
| 154 | races. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 155 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 156 | - Limitations on the size of program that can run have been removed. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 157 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 158 | - Performance has been modestly improved, although that is very |
| 159 | workload-dependent. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 160 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 161 | - Direct support for Qt4 threading has been added. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 162 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 163 | - pthread_barriers are now directly supported. |
njn | 75010ca | 2008-02-09 05:10:45 +0000 | [diff] [blame] | 164 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 165 | - Helgrind works well on all supported Linux targets. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 166 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 167 | * The DRD thread debugging tool has seen major improvements: |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 168 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 169 | - Greatly improved performance and significantly reduced memory |
| 170 | usage. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 171 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 172 | - Support for several major threading libraries (Boost.Thread, Qt4, |
| 173 | glib, OpenMP) has been added. |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 174 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 175 | - Support for atomic instructions, POSIX semaphores, barriers and |
| 176 | reader-writer locks has been added. |
| 177 | |
| 178 | - Works now on PowerPC CPUs too. |
| 179 | |
| 180 | - Added support for printing thread stack usage at thread exit time. |
| 181 | |
| 182 | - Added support for debugging lock contention. |
| 183 | |
| 184 | - Added a manual for Drd. |
| 185 | |
| 186 | * A new experimental tool, exp-Ptrcheck, has been added. Ptrcheck |
| 187 | checks for misuses of pointers. In that sense it is a bit like |
| 188 | Memcheck. However, Ptrcheck can do things Memcheck can't: it can |
| 189 | detect overruns of stack and global arrays, it can detect |
| 190 | arbitrarily far out-of-bounds accesses to heap blocks, and it can |
| 191 | detect accesses heap blocks that have been freed a very long time |
| 192 | ago (millions of blocks in the past). |
| 193 | |
| 194 | Ptrcheck currently works only on x86-linux and amd64-linux. To use |
| 195 | it, use --tool=exp-ptrcheck. A simple manual is provided, as part |
| 196 | of the main Valgrind documentation. As this is an experimental |
| 197 | tool, we would be particularly interested in hearing about your |
| 198 | experiences with it. |
| 199 | |
sewardj | 974aace | 2008-12-24 18:40:57 +0000 | [diff] [blame] | 200 | * exp-Omega, an experimental instantaneous leak-detecting tool, is no |
| 201 | longer built by default, although the code remains in the repository |
| 202 | and the tarball. This is due to three factors: a perceived lack of |
| 203 | users, a lack of maintenance, and concerns that it may not be |
| 204 | possible to achieve reliable operation using the existing design. |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 205 | |
| 206 | * As usual, support for the latest Linux distros and toolchain |
| 207 | components has been added. It should work well on Fedora Core 10, |
| 208 | OpenSUSE 11.1 and Ubuntu 8.10. gcc-4.4 (in its current pre-release |
| 209 | state) is supported, as is glibc-2.9. The C++ demangler has been |
| 210 | updated so as to work well with C++ compiled by even the most recent |
| 211 | g++'s. |
| 212 | |
| 213 | * You can now use frame-level wildcards in suppressions. This was a |
| 214 | frequently-requested enhancement. A line "..." in a suppression now |
| 215 | matches zero or more frames. This makes it easier to write |
| 216 | suppressions which are precise yet insensitive to changes in |
| 217 | inlining behaviour. |
| 218 | |
| 219 | * 3.4.0 adds support on x86/amd64 for the SSSE3 instruction set. |
| 220 | |
| 221 | * Very basic support for IBM Power6 has been added (64-bit processes only). |
| 222 | |
| 223 | * Valgrind is now cross-compilable. For example, it is possible to |
| 224 | cross compile Valgrind on an x86/amd64-linux host, so that it runs |
| 225 | on a ppc32/64-linux target. |
| 226 | |
sewardj | f1fa5ed | 2008-12-23 17:04:52 +0000 | [diff] [blame] | 227 | * You can set the main thread's stack size at startup using the |
| 228 | new --main-stacksize= flag (subject of course to ulimit settings). |
| 229 | This is useful for running apps that need a lot of stack space. |
| 230 | |
| 231 | * The limitation that you can't use --trace-children=yes together |
| 232 | with --db-attach=yes has been removed. |
| 233 | |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 234 | * The following bugs have been fixed. Note that "n-i-bz" stands for |
| 235 | "not in bugzilla" -- that is, a bug that was reported to us but |
| 236 | never got a bugzilla entry. We encourage you to file bugs in |
| 237 | bugzilla (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than |
| 238 | mailing the developers (or mailing lists) directly. |
| 239 | |
sewardj | f1fa5ed | 2008-12-23 17:04:52 +0000 | [diff] [blame] | 240 | n-i-bz Make return types for some client requests 64-bit clean |
| 241 | n-i-bz glibc 2.9 support |
| 242 | n-i-bz ignore unsafe .valgrindrc's (CVE-2008-4865) |
| 243 | n-i-bz MPI_Init(0,0) is valid but libmpiwrap.c segfaults |
| 244 | n-i-bz Building in an env without gdb gives bogus gdb attach |
| 245 | 92456 Tracing the origin of uninitialised memory |
| 246 | 106497 Valgrind does not demangle some C++ template symbols |
| 247 | 162222 ==106497 |
sewardj | df1fc9a | 2008-12-23 23:09:57 +0000 | [diff] [blame] | 248 | 151612 Suppression with "..." (frame-level wildcards in .supp files) |
sewardj | f1fa5ed | 2008-12-23 17:04:52 +0000 | [diff] [blame] | 249 | 156404 Unable to start oocalc under memcheck on openSUSE 10.3 (64-bit) |
| 250 | 159285 unhandled syscall:25 (stime, on x86-linux) |
| 251 | 159452 unhandled ioctl 0x8B01 on "valgrind iwconfig" |
| 252 | 160954 ppc build of valgrind crashes with illegal instruction (isel) |
| 253 | 160956 mallinfo implementation, w/ patch |
| 254 | 162092 Valgrind fails to start gnome-system-monitor |
| 255 | 162819 malloc_free_fill test doesn't pass on glibc2.8 x86 |
| 256 | 163794 assertion failure with "--track-origins=yes" |
| 257 | 163933 sigcontext.err and .trapno must be set together |
| 258 | 163955 remove constraint !(--db-attach=yes && --trace-children=yes) |
| 259 | 164476 Missing kernel module loading system calls |
| 260 | 164669 SVN regression: mmap() drops posix file locks |
| 261 | 166581 Callgrind output corruption when program forks |
| 262 | 167288 Patch file for missing system calls on Cell BE |
| 263 | 168943 unsupported scas instruction pentium |
| 264 | 171645 Unrecognised instruction (MOVSD, non-binutils encoding) |
| 265 | 172417 x86->IR: 0x82 ... |
| 266 | 172563 amd64->IR: 0xD9 0xF5 - fprem1 |
| 267 | 173099 .lds linker script generation error |
| 268 | 173177 [x86_64] syscalls: 125/126/179 (capget/capset/quotactl) |
| 269 | 173751 amd64->IR: 0x48 0xF 0x6F 0x45 (even more redundant prefixes) |
| 270 | 174532 == 173751 |
| 271 | 174908 --log-file value not expanded correctly for core file |
| 272 | 175044 Add lookup_dcookie for amd64 |
| 273 | 175150 x86->IR: 0xF2 0xF 0x11 0xC1 (movss non-binutils encoding) |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 274 | |
| 275 | Developer-visible changes: |
| 276 | |
| 277 | * Valgrind's debug-info reading machinery has been majorly overhauled. |
| 278 | It can now correctly establish the addresses for ELF data symbols, |
| 279 | which is something that has never worked properly before now. |
| 280 | |
| 281 | Also, Valgrind can now read DWARF3 type and location information for |
| 282 | stack and global variables. This makes it possible to use the |
| 283 | framework to build tools that rely on knowing the type and locations |
| 284 | of stack and global variables, for example exp-Ptrcheck. |
| 285 | |
| 286 | Reading of such information is disabled by default, because most |
| 287 | tools don't need it, and because it is expensive in space and time. |
| 288 | However, you can force Valgrind to read it, using the |
| 289 | --read-var-info=yes flag. Memcheck, Helgrind and DRD are able to |
| 290 | make use of such information, if present, to provide source-level |
| 291 | descriptions of data addresses in the error messages they create. |
| 292 | |
sewardj | 974aace | 2008-12-24 18:40:57 +0000 | [diff] [blame] | 293 | (3.4.0.RC1: 24 Dec 2008, vex r1878, valgrind r8882). |
sewardj | b8b1664 | 2009-01-02 23:21:54 +0000 | [diff] [blame] | 294 | (3.4.0: 3 Jan 2009, vex r1878, valgrind r8899). |
sewardj | 565fcf1 | 2008-12-23 13:14:06 +0000 | [diff] [blame] | 295 | |
sewardj | 8639f11 | 2008-12-17 12:26:24 +0000 | [diff] [blame] | 296 | |
sewardj | 9f42ba3 | 2008-06-04 11:47:51 +0000 | [diff] [blame] | 297 | |
| 298 | Release 3.3.1 (4 June 2008) |
| 299 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 300 | 3.3.1 fixes a bunch of bugs in 3.3.0, adds support for glibc-2.8 based |
| 301 | systems (openSUSE 11, Fedora Core 9), improves the existing glibc-2.7 |
| 302 | support, and adds support for the SSSE3 (Core 2) instruction set. |
| 303 | |
| 304 | 3.3.1 will likely be the last release that supports some very old |
| 305 | systems. In particular, the next major release, 3.4.0, will drop |
| 306 | support for the old LinuxThreads threading library, and for gcc |
| 307 | versions prior to 3.0. |
| 308 | |
| 309 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 310 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 311 | bugzilla entry. We encourage you to file bugs in bugzilla |
| 312 | (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than mailing the |
| 313 | developers (or mailing lists) directly -- bugs that are not entered |
| 314 | into bugzilla tend to get forgotten about or ignored. |
| 315 | |
| 316 | n-i-bz Massif segfaults at exit |
| 317 | n-i-bz Memcheck asserts on Altivec code |
| 318 | n-i-bz fix sizeof bug in Helgrind |
| 319 | n-i-bz check fd on sys_llseek |
| 320 | n-i-bz update syscall lists to kernel 2.6.23.1 |
| 321 | n-i-bz support sys_sync_file_range |
| 322 | n-i-bz handle sys_sysinfo, sys_getresuid, sys_getresgid on ppc64-linux |
| 323 | n-i-bz intercept memcpy in 64-bit ld.so's |
| 324 | n-i-bz Fix wrappers for sys_{futimesat,utimensat} |
| 325 | n-i-bz Minor false-error avoidance fixes for Memcheck |
| 326 | n-i-bz libmpiwrap.c: add a wrapper for MPI_Waitany |
| 327 | n-i-bz helgrind support for glibc-2.8 |
| 328 | n-i-bz partial fix for mc_leakcheck.c:698 assert: |
| 329 | 'lc_shadows[i]->data + lc_shadows[i] ... |
| 330 | n-i-bz Massif/Cachegrind output corruption when programs fork |
| 331 | n-i-bz register allocator fix: handle spill stores correctly |
| 332 | n-i-bz add support for PA6T PowerPC CPUs |
| 333 | 126389 vex x86->IR: 0xF 0xAE (FXRSTOR) |
| 334 | 158525 ==126389 |
| 335 | 152818 vex x86->IR: 0xF3 0xAC (repz lodsb) |
| 336 | 153196 vex x86->IR: 0xF2 0xA6 (repnz cmpsb) |
| 337 | 155011 vex x86->IR: 0xCF (iret) |
| 338 | 155091 Warning [...] unhandled DW_OP_ opcode 0x23 |
| 339 | 156960 ==155901 |
| 340 | 155528 support Core2/SSSE3 insns on x86/amd64 |
| 341 | 155929 ms_print fails on massif outputs containing long lines |
| 342 | 157665 valgrind fails on shmdt(0) after shmat to 0 |
| 343 | 157748 support x86 PUSHFW/POPFW |
| 344 | 158212 helgrind: handle pthread_rwlock_try{rd,wr}lock. |
| 345 | 158425 sys_poll incorrectly emulated when RES==0 |
| 346 | 158744 vex amd64->IR: 0xF0 0x41 0xF 0xC0 (xaddb) |
| 347 | 160907 Support for a couple of recent Linux syscalls |
| 348 | 161285 Patch -- support for eventfd() syscall |
| 349 | 161378 illegal opcode in debug libm (FUCOMPP) |
| 350 | 160136 ==161378 |
| 351 | 161487 number of suppressions files is limited to 10 |
| 352 | 162386 ms_print typo in milliseconds time unit for massif |
| 353 | 161036 exp-drd: client allocated memory was never freed |
| 354 | 162663 signalfd_wrapper fails on 64bit linux |
| 355 | |
| 356 | (3.3.1.RC1: 2 June 2008, vex r1854, valgrind r8169). |
| 357 | (3.3.1: 4 June 2008, vex r1854, valgrind r8180). |
| 358 | |
| 359 | |
| 360 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 361 | Release 3.3.0 (7 December 2007) |
| 362 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 363 | 3.3.0 is a feature release with many significant improvements and the |
| 364 | usual collection of bug fixes. This release supports X86/Linux, |
| 365 | AMD64/Linux, PPC32/Linux and PPC64/Linux. Support for recent distros |
| 366 | (using gcc 4.3, glibc 2.6 and 2.7) has been added. |
njn | f4f9cd4 | 2007-11-23 01:42:10 +0000 | [diff] [blame] | 367 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 368 | The main excitement in 3.3.0 is new and improved tools. Helgrind |
| 369 | works again, Massif has been completely overhauled and much improved, |
| 370 | Cachegrind now does branch-misprediction profiling, and a new category |
| 371 | of experimental tools has been created, containing two new tools: |
| 372 | Omega and DRD. There are many other smaller improvements. In detail: |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 373 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 374 | - Helgrind has been completely overhauled and works for the first time |
| 375 | since Valgrind 2.2.0. Supported functionality is: detection of |
| 376 | misuses of the POSIX PThreads API, detection of potential deadlocks |
| 377 | resulting from cyclic lock dependencies, and detection of data |
| 378 | races. Compared to the 2.2.0 Helgrind, the race detection algorithm |
| 379 | has some significant improvements aimed at reducing the false error |
| 380 | rate. Handling of various kinds of corner cases has been improved. |
| 381 | Efforts have been made to make the error messages easier to |
| 382 | understand. Extensive documentation is provided. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 383 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 384 | - Massif has been completely overhauled. Instead of measuring |
| 385 | space-time usage -- which wasn't always useful and many people found |
| 386 | confusing -- it now measures space usage at various points in the |
| 387 | execution, including the point of peak memory allocation. Its |
| 388 | output format has also changed: instead of producing PostScript |
| 389 | graphs and HTML text, it produces a single text output (via the new |
| 390 | 'ms_print' script) that contains both a graph and the old textual |
| 391 | information, but in a more compact and readable form. Finally, the |
| 392 | new version should be more reliable than the old one, as it has been |
| 393 | tested more thoroughly. |
njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 394 | |
sewardj | 8badbaa | 2007-05-08 09:20:25 +0000 | [diff] [blame] | 395 | - Cachegrind has been extended to do branch-misprediction profiling. |
| 396 | Both conditional and indirect branches are profiled. The default |
| 397 | behaviour of Cachegrind is unchanged. To use the new functionality, |
| 398 | give the option --branch-sim=yes. |
| 399 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 400 | - A new category of "experimental tools" has been created. Such tools |
| 401 | may not work as well as the standard tools, but are included because |
| 402 | some people will find them useful, and because exposure to a wider |
| 403 | user group provides tool authors with more end-user feedback. These |
| 404 | tools have a "exp-" prefix attached to their names to indicate their |
| 405 | experimental nature. Currently there are two experimental tools: |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 406 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 407 | * exp-Omega: an instantaneous leak detector. See |
| 408 | exp-omega/docs/omega_introduction.txt. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 409 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 410 | * exp-DRD: a data race detector based on the happens-before |
sewardj | 8b09d4f | 2007-12-04 21:27:18 +0000 | [diff] [blame] | 411 | relation. See exp-drd/docs/README.txt. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 412 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 413 | - Scalability improvements for very large programs, particularly those |
| 414 | which have a million or more malloc'd blocks in use at once. These |
| 415 | improvements mostly affect Memcheck. Memcheck is also up to 10% |
| 416 | faster for all programs, with x86-linux seeing the largest |
| 417 | improvement. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 418 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 419 | - Works well on the latest Linux distros. Has been tested on Fedora |
| 420 | Core 8 (x86, amd64, ppc32, ppc64) and openSUSE 10.3. glibc 2.6 and |
| 421 | 2.7 are supported. gcc-4.3 (in its current pre-release state) is |
| 422 | supported. At the same time, 3.3.0 retains support for older |
| 423 | distros. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 424 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 425 | - The documentation has been modestly reorganised with the aim of |
| 426 | making it easier to find information on common-usage scenarios. |
| 427 | Some advanced material has been moved into a new chapter in the main |
| 428 | manual, so as to unclutter the main flow, and other tidying up has |
| 429 | been done. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 430 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 431 | - There is experimental support for AIX 5.3, both 32-bit and 64-bit |
| 432 | processes. You need to be running a 64-bit kernel to use Valgrind |
| 433 | on a 64-bit executable. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 434 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 435 | - There have been some changes to command line options, which may |
| 436 | affect you: |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 437 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 438 | * --log-file-exactly and |
| 439 | --log-file-qualifier options have been removed. |
njn | 374a36d | 2007-11-23 01:41:32 +0000 | [diff] [blame] | 440 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 441 | To make up for this --log-file option has been made more powerful. |
| 442 | It now accepts a %p format specifier, which is replaced with the |
| 443 | process ID, and a %q{FOO} format specifier, which is replaced with |
| 444 | the contents of the environment variable FOO. |
| 445 | |
| 446 | * --child-silent-after-fork=yes|no [no] |
| 447 | |
| 448 | Causes Valgrind to not show any debugging or logging output for |
| 449 | the child process resulting from a fork() call. This can make the |
| 450 | output less confusing (although more misleading) when dealing with |
| 451 | processes that create children. |
| 452 | |
| 453 | * --cachegrind-out-file, --callgrind-out-file and --massif-out-file |
| 454 | |
| 455 | These control the names of the output files produced by |
| 456 | Cachegrind, Callgrind and Massif. They accept the same %p and %q |
| 457 | format specifiers that --log-file accepts. --callgrind-out-file |
| 458 | replaces Callgrind's old --base option. |
| 459 | |
| 460 | * Cachegrind's 'cg_annotate' script no longer uses the --<pid> |
| 461 | option to specify the output file. Instead, the first non-option |
| 462 | argument is taken to be the name of the output file, and any |
| 463 | subsequent non-option arguments are taken to be the names of |
| 464 | source files to be annotated. |
| 465 | |
| 466 | * Cachegrind and Callgrind now use directory names where possible in |
| 467 | their output files. This means that the -I option to |
| 468 | 'cg_annotate' and 'callgrind_annotate' should not be needed in |
| 469 | most cases. It also means they can correctly handle the case |
| 470 | where two source files in different directories have the same |
| 471 | name. |
| 472 | |
| 473 | - Memcheck offers a new suppression kind: "Jump". This is for |
| 474 | suppressing jump-to-invalid-address errors. Previously you had to |
| 475 | use an "Addr1" suppression, which didn't make much sense. |
| 476 | |
| 477 | - Memcheck has new flags --malloc-fill=<hexnum> and |
| 478 | --free-fill=<hexnum> which free malloc'd / free'd areas with the |
| 479 | specified byte. This can help shake out obscure memory corruption |
| 480 | problems. The definedness and addressibility of these areas is |
| 481 | unchanged -- only the contents are affected. |
njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 482 | |
| 483 | - The behaviour of Memcheck's client requests VALGRIND_GET_VBITS and |
| 484 | VALGRIND_SET_VBITS have changed slightly. They no longer issue |
| 485 | addressability errors -- if either array is partially unaddressable, |
| 486 | they just return 3 (as before). Also, SET_VBITS doesn't report |
| 487 | definedness errors if any of the V bits are undefined. |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 488 | |
njn | 92676d7 | 2007-12-04 21:18:06 +0000 | [diff] [blame] | 489 | - The following Memcheck client requests have been removed: |
| 490 | VALGRIND_MAKE_NOACCESS |
| 491 | VALGRIND_MAKE_WRITABLE |
| 492 | VALGRIND_MAKE_READABLE |
| 493 | VALGRIND_CHECK_WRITABLE |
| 494 | VALGRIND_CHECK_READABLE |
| 495 | VALGRIND_CHECK_DEFINED |
| 496 | They were deprecated in 3.2.0, when equivalent but better-named client |
| 497 | requests were added. See the 3.2.0 release notes for more details. |
| 498 | |
njn | 5a0a773 | 2007-02-12 10:37:37 +0000 | [diff] [blame] | 499 | - The behaviour of the tool Lackey has changed slightly. First, the output |
| 500 | from --trace-mem has been made more compact, to reduce the size of the |
| 501 | traces. Second, a new option --trace-superblocks has been added, which |
| 502 | shows the addresses of superblocks (code blocks) as they are executed. |
| 503 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 504 | - The following bugs have been fixed. Note that "n-i-bz" stands for |
| 505 | "not in bugzilla" -- that is, a bug that was reported to us but |
| 506 | never got a bugzilla entry. We encourage you to file bugs in |
| 507 | bugzilla (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than |
| 508 | mailing the developers (or mailing lists) directly. |
| 509 | |
| 510 | n-i-bz x86_linux_REDIR_FOR_index() broken |
| 511 | n-i-bz guest-amd64/toIR.c:2512 (dis_op2_E_G): Assertion `0' failed. |
| 512 | n-i-bz Support x86 INT insn (INT (0xCD) 0x40 - 0x43) |
| 513 | n-i-bz Add sys_utimensat system call for Linux x86 platform |
| 514 | 79844 Helgrind complains about race condition which does not exist |
| 515 | 82871 Massif output function names too short |
| 516 | 89061 Massif: ms_main.c:485 (get_XCon): Assertion `xpt->max_chi...' |
| 517 | 92615 Write output from Massif at crash |
| 518 | 95483 massif feature request: include peak allocation in report |
| 519 | 112163 MASSIF crashed with signal 7 (SIGBUS) after running 2 days |
| 520 | 119404 problems running setuid executables (partial fix) |
| 521 | 121629 add instruction-counting mode for timing |
| 522 | 127371 java vm giving unhandled instruction bytes: 0x26 0x2E 0x64 0x65 |
| 523 | 129937 ==150380 |
| 524 | 129576 Massif loses track of memory, incorrect graphs |
| 525 | 132132 massif --format=html output does not do html entity escaping |
| 526 | 132950 Heap alloc/usage summary |
| 527 | 133962 unhandled instruction bytes: 0xF2 0x4C 0xF 0x10 |
| 528 | 134990 use -fno-stack-protector if possible |
| 529 | 136382 ==134990 |
| 530 | 137396 I would really like helgrind to work again... |
| 531 | 137714 x86/amd64->IR: 0x66 0xF 0xF7 0xC6 (maskmovq, maskmovdq) |
| 532 | 141631 Massif: percentages don't add up correctly |
| 533 | 142706 massif numbers don't seem to add up |
| 534 | 143062 massif crashes on app exit with signal 8 SIGFPE |
| 535 | 144453 (get_XCon): Assertion 'xpt->max_children != 0' failed. |
| 536 | 145559 valgrind aborts when malloc_stats is called |
| 537 | 145609 valgrind aborts all runs with 'repeated section!' |
| 538 | 145622 --db-attach broken again on x86-64 |
| 539 | 145837 ==149519 |
| 540 | 145887 PPC32: getitimer() system call is not supported |
| 541 | 146252 ==150678 |
| 542 | 146456 (update_XCon): Assertion 'xpt->curr_space >= -space_delta'... |
| 543 | 146701 ==134990 |
| 544 | 146781 Adding support for private futexes |
| 545 | 147325 valgrind internal error on syscall (SYS_io_destroy, 0) |
| 546 | 147498 amd64->IR: 0xF0 0xF 0xB0 0xF (lock cmpxchg %cl,(%rdi)) |
sewardj | bc39ad2 | 2007-12-09 02:24:02 +0000 | [diff] [blame] | 547 | 147545 Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 548 | 147628 SALC opcode 0xd6 unimplemented |
| 549 | 147825 crash on amd64-linux with gcc 4.2 and glibc 2.6 (CFI) |
| 550 | 148174 Incorrect type of freed_list_volume causes assertion [...] |
| 551 | 148447 x86_64 : new NOP codes: 66 66 66 66 2e 0f 1f |
| 552 | 149182 PPC Trap instructions not implemented in valgrind |
| 553 | 149504 Assertion hit on alloc_xpt->curr_space >= -space_delta |
| 554 | 149519 ppc32: V aborts with SIGSEGV on execution of a signal handler |
| 555 | 149892 ==137714 |
| 556 | 150044 SEGV during stack deregister |
| 557 | 150380 dwarf/gcc interoperation (dwarf3 read problems) |
| 558 | 150408 ==148447 |
| 559 | 150678 guest-amd64/toIR.c:3741 (dis_Grp5): Assertion `sz == 4' failed |
| 560 | 151209 V unable to execute programs for users with UID > 2^16 |
| 561 | 151938 help on --db-command= misleading |
| 562 | 152022 subw $0x28, %%sp causes assertion failure in memcheck |
| 563 | 152357 inb and outb not recognized in 64-bit mode |
| 564 | 152501 vex x86->IR: 0x27 0x66 0x89 0x45 (daa) |
| 565 | 152818 vex x86->IR: 0xF3 0xAC 0xFC 0x9C (rep lodsb) |
| 566 | |
njn | d5f4bef | 2006-12-24 07:54:19 +0000 | [diff] [blame] | 567 | Developer-visible changes: |
| 568 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 569 | - The names of some functions and types within the Vex IR have |
| 570 | changed. Run 'svn log -r1689 VEX/pub/libvex_ir.h' for full details. |
| 571 | Any existing standalone tools will have to be updated to reflect |
| 572 | these changes. The new names should be clearer. The file |
| 573 | VEX/pub/libvex_ir.h is also much better commented. |
njn | d8366ee | 2007-02-12 22:38:50 +0000 | [diff] [blame] | 574 | |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 575 | - A number of new debugging command line options have been added. |
| 576 | These are mostly of use for debugging the symbol table and line |
| 577 | number readers: |
| 578 | |
| 579 | --trace-symtab-patt=<patt> limit debuginfo tracing to obj name <patt> |
| 580 | --trace-cfi=no|yes show call-frame-info details? [no] |
| 581 | --debug-dump=syms mimic /usr/bin/readelf --syms |
| 582 | --debug-dump=line mimic /usr/bin/readelf --debug-dump=line |
| 583 | --debug-dump=frames mimic /usr/bin/readelf --debug-dump=frames |
| 584 | --sym-offsets=yes|no show syms in form 'name+offset' ? [no] |
| 585 | |
| 586 | - Internally, the code base has been further factorised and |
| 587 | abstractified, particularly with respect to support for non-Linux |
| 588 | OSs. |
| 589 | |
sewardj | 135a7ff | 2007-12-10 22:17:42 +0000 | [diff] [blame] | 590 | (3.3.0.RC1: 2 Dec 2007, vex r1803, valgrind r7268). |
| 591 | (3.3.0.RC2: 5 Dec 2007, vex r1804, valgrind r7282). |
| 592 | (3.3.0.RC3: 9 Dec 2007, vex r1804, valgrind r7288). |
sewardj | 686b5be | 2007-12-10 22:21:14 +0000 | [diff] [blame] | 593 | (3.3.0: 10 Dec 2007, vex r1804, valgrind r7290). |
sewardj | cb2288b | 2007-12-02 02:08:17 +0000 | [diff] [blame] | 594 | |
njn | d5f4bef | 2006-12-24 07:54:19 +0000 | [diff] [blame] | 595 | |
| 596 | |
njn | 9923775 | 2007-01-30 05:18:38 +0000 | [diff] [blame] | 597 | Release 3.2.3 (29 Jan 2007) |
| 598 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 599 | Unfortunately 3.2.2 introduced a regression which can cause an |
| 600 | assertion failure ("vex: the `impossible' happened: eqIRConst") when |
| 601 | running obscure pieces of SSE code. 3.2.3 fixes this and adds one |
| 602 | more glibc-2.5 intercept. In all other respects it is identical to |
| 603 | 3.2.2. Please do not use (or package) 3.2.2; instead use 3.2.3. |
| 604 | |
| 605 | n-i-bz vex: the `impossible' happened: eqIRConst |
| 606 | n-i-bz Add an intercept for glibc-2.5 __stpcpy_chk |
| 607 | |
| 608 | (3.2.3: 29 Jan 2007, vex r1732, valgrind r6560). |
| 609 | |
| 610 | |
njn | a7e4880 | 2007-01-23 05:58:52 +0000 | [diff] [blame] | 611 | Release 3.2.2 (22 Jan 2007) |
| 612 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 613 | 3.2.2 fixes a bunch of bugs in 3.2.1, adds support for glibc-2.5 based |
| 614 | systems (openSUSE 10.2, Fedora Core 6), improves support for icc-9.X |
| 615 | compiled code, and brings modest performance improvements in some |
| 616 | areas, including amd64 floating point, powerpc support, and startup |
| 617 | responsiveness on all targets. |
| 618 | |
| 619 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 620 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 621 | bugzilla entry. We encourage you to file bugs in bugzilla |
| 622 | (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than mailing the |
| 623 | developers (or mailing lists) directly. |
| 624 | |
| 625 | 129390 ppc?->IR: some kind of VMX prefetch (dstt) |
| 626 | 129968 amd64->IR: 0xF 0xAE 0x0 (fxsave) |
| 627 | 134319 ==129968 |
| 628 | 133054 'make install' fails with syntax errors |
| 629 | 118903 ==133054 |
| 630 | 132998 startup fails in when running on UML |
| 631 | 134207 pkg-config output contains @VG_PLATFORM@ |
| 632 | 134727 valgrind exits with "Value too large for defined data type" |
| 633 | n-i-bz ppc32/64: support mcrfs |
| 634 | n-i-bz Cachegrind/Callgrind: Update cache parameter detection |
| 635 | 135012 x86->IR: 0xD7 0x8A 0xE0 0xD0 (xlat) |
| 636 | 125959 ==135012 |
| 637 | 126147 x86->IR: 0xF2 0xA5 0xF 0x77 (repne movsw) |
| 638 | 136650 amd64->IR: 0xC2 0x8 0x0 |
| 639 | 135421 x86->IR: unhandled Grp5(R) case 6 |
| 640 | n-i-bz Improved documentation of the IR intermediate representation |
| 641 | n-i-bz jcxz (x86) (users list, 8 Nov) |
| 642 | n-i-bz ExeContext hashing fix |
| 643 | n-i-bz fix CFI reading failures ("Dwarf CFI 0:24 0:32 0:48 0:7") |
| 644 | n-i-bz fix Cachegrind/Callgrind simulation bug |
| 645 | n-i-bz libmpiwrap.c: fix handling of MPI_LONG_DOUBLE |
| 646 | n-i-bz make User errors suppressible |
| 647 | 136844 corrupted malloc line when using --gen-suppressions=yes |
| 648 | 138507 ==136844 |
| 649 | n-i-bz Speed up the JIT's register allocator |
| 650 | n-i-bz Fix confusing leak-checker flag hints |
| 651 | n-i-bz Support recent autoswamp versions |
| 652 | n-i-bz ppc32/64 dispatcher speedups |
| 653 | n-i-bz ppc64 front end rld/rlw improvements |
| 654 | n-i-bz ppc64 back end imm64 improvements |
| 655 | 136300 support 64K pages on ppc64-linux |
| 656 | 139124 == 136300 |
| 657 | n-i-bz fix ppc insn set tests for gcc >= 4.1 |
| 658 | 137493 x86->IR: recent binutils no-ops |
| 659 | 137714 x86->IR: 0x66 0xF 0xF7 0xC6 (maskmovdqu) |
| 660 | 138424 "failed in UME with error 22" (produce a better error msg) |
| 661 | 138856 ==138424 |
| 662 | 138627 Enhancement support for prctl ioctls |
| 663 | 138896 Add support for usb ioctls |
| 664 | 136059 ==138896 |
| 665 | 139050 ppc32->IR: mfspr 268/269 instructions not handled |
| 666 | n-i-bz ppc32->IR: lvxl/stvxl |
| 667 | n-i-bz glibc-2.5 support |
| 668 | n-i-bz memcheck: provide replacement for mempcpy |
| 669 | n-i-bz memcheck: replace bcmp in ld.so |
| 670 | n-i-bz Use 'ifndef' in VEX's Makefile correctly |
| 671 | n-i-bz Suppressions for MVL 4.0.1 on ppc32-linux |
| 672 | n-i-bz libmpiwrap.c: Fixes for MPICH |
| 673 | n-i-bz More robust handling of hinted client mmaps |
| 674 | 139776 Invalid read in unaligned memcpy with Intel compiler v9 |
| 675 | n-i-bz Generate valid XML even for very long fn names |
| 676 | n-i-bz Don't prompt about suppressions for unshown reachable leaks |
| 677 | 139910 amd64 rcl is not supported |
| 678 | n-i-bz DWARF CFI reader: handle DW_CFA_undefined |
| 679 | n-i-bz DWARF CFI reader: handle icc9 generated CFI info better |
| 680 | n-i-bz fix false uninit-value errs in icc9 generated FP code |
| 681 | n-i-bz reduce extraneous frames in libmpiwrap.c |
| 682 | n-i-bz support pselect6 on amd64-linux |
| 683 | |
| 684 | (3.2.2: 22 Jan 2007, vex r1729, valgrind r6545). |
| 685 | |
| 686 | |
sewardj | 172bce8 | 2006-09-16 01:00:35 +0000 | [diff] [blame] | 687 | Release 3.2.1 (16 Sept 2006) |
| 688 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 689 | 3.2.1 adds x86/amd64 support for all SSE3 instructions except monitor |
| 690 | and mwait, further reduces memcheck's false error rate on all |
| 691 | platforms, adds support for recent binutils (in OpenSUSE 10.2 and |
| 692 | Fedora Rawhide) and fixes a bunch of bugs in 3.2.0. Some of the fixed |
| 693 | bugs were causing large programs to segfault with --tool=callgrind and |
| 694 | --tool=cachegrind, so an upgrade is recommended. |
| 695 | |
| 696 | In view of the fact that any 3.3.0 release is unlikely to happen until |
| 697 | well into 1Q07, we intend to keep the 3.2.X line alive for a while |
| 698 | yet, and so we tentatively plan a 3.2.2 release sometime in December |
| 699 | 06. |
| 700 | |
| 701 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 702 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 703 | bugzilla entry. |
| 704 | |
| 705 | n-i-bz Expanding brk() into last available page asserts |
| 706 | n-i-bz ppc64-linux stack RZ fast-case snafu |
| 707 | n-i-bz 'c' in --gen-supps=yes doesn't work |
| 708 | n-i-bz VG_N_SEGMENTS too low (users, 28 June) |
| 709 | n-i-bz VG_N_SEGNAMES too low (Stu Robinson) |
| 710 | 106852 x86->IR: fisttp (SSE3) |
| 711 | 117172 FUTEX_WAKE does not use uaddr2 |
| 712 | 124039 Lacks support for VKI_[GP]IO_UNIMAP* |
| 713 | 127521 amd64->IR: 0xF0 0x48 0xF 0xC7 (cmpxchg8b) |
| 714 | 128917 amd64->IR: 0x66 0xF 0xF6 0xC4 (psadbw,SSE2) |
| 715 | 129246 JJ: ppc32/ppc64 syscalls, w/ patch |
| 716 | 129358 x86->IR: fisttpl (SSE3) |
| 717 | 129866 cachegrind/callgrind causes executable to die |
| 718 | 130020 Can't stat .so/.exe error while reading symbols |
| 719 | 130388 Valgrind aborts when process calls malloc_trim() |
| 720 | 130638 PATCH: ppc32 missing system calls |
| 721 | 130785 amd64->IR: unhandled instruction "pushfq" |
| 722 | 131481: (HINT_NOP) vex x86->IR: 0xF 0x1F 0x0 0xF |
| 723 | 131298 ==131481 |
| 724 | 132146 Programs with long sequences of bswap[l,q]s |
| 725 | 132918 vex amd64->IR: 0xD9 0xF8 (fprem) |
| 726 | 132813 Assertion at priv/guest-x86/toIR.c:652 fails |
| 727 | 133051 'cfsi->len > 0 && cfsi->len < 2000000' failed |
| 728 | 132722 valgrind header files are not standard C |
| 729 | n-i-bz Livelocks entire machine (users list, Timothy Terriberry) |
| 730 | n-i-bz Alex Bennee mmap problem (9 Aug) |
| 731 | n-i-bz BartV: Don't print more lines of a stack-trace than were obtained. |
| 732 | n-i-bz ppc32 SuSE 10.1 redir |
| 733 | n-i-bz amd64 padding suppressions |
| 734 | n-i-bz amd64 insn printing fix. |
| 735 | n-i-bz ppc cmp reg,reg fix |
| 736 | n-i-bz x86/amd64 iropt e/rflag reduction rules |
| 737 | n-i-bz SuSE 10.1 (ppc32) minor fixes |
| 738 | 133678 amd64->IR: 0x48 0xF 0xC5 0xC0 (pextrw?) |
| 739 | 133694 aspacem assertion: aspacem_minAddr <= holeStart |
| 740 | n-i-bz callgrind: fix warning about malformed creator line |
| 741 | n-i-bz callgrind: fix annotate script for data produced with |
| 742 | --dump-instr=yes |
| 743 | n-i-bz callgrind: fix failed assertion when toggling |
| 744 | instrumentation mode |
| 745 | n-i-bz callgrind: fix annotate script fix warnings with |
| 746 | --collect-jumps=yes |
| 747 | n-i-bz docs path hardwired (Dennis Lubert) |
| 748 | |
| 749 | The following bugs were not fixed, due primarily to lack of developer |
| 750 | time, and also because bug reporters did not answer requests for |
| 751 | feedback in time for the release: |
| 752 | |
| 753 | 129390 ppc?->IR: some kind of VMX prefetch (dstt) |
| 754 | 129968 amd64->IR: 0xF 0xAE 0x0 (fxsave) |
| 755 | 133054 'make install' fails with syntax errors |
| 756 | n-i-bz Signal race condition (users list, 13 June, Johannes Berg) |
| 757 | n-i-bz Unrecognised instruction at address 0x70198EC2 (users list, |
| 758 | 19 July, Bennee) |
| 759 | 132998 startup fails in when running on UML |
| 760 | |
| 761 | The following bug was tentatively fixed on the mainline but the fix |
| 762 | was considered too risky to push into 3.2.X: |
| 763 | |
| 764 | 133154 crash when using client requests to register/deregister stack |
| 765 | |
| 766 | (3.2.1: 16 Sept 2006, vex r1658, valgrind r6070). |
| 767 | |
| 768 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 769 | Release 3.2.0 (7 June 2006) |
sewardj | 535a235 | 2006-04-18 02:04:52 +0000 | [diff] [blame] | 770 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 771 | 3.2.0 is a feature release with many significant improvements and the |
| 772 | usual collection of bug fixes. This release supports X86/Linux, |
| 773 | AMD64/Linux, PPC32/Linux and PPC64/Linux. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 774 | |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 775 | Performance, especially of Memcheck, is improved, Addrcheck has been |
| 776 | removed, Callgrind has been added, PPC64/Linux support has been added, |
| 777 | Lackey has been improved, and MPI support has been added. In detail: |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 778 | |
sewardj | f41db3c | 2006-05-26 16:06:10 +0000 | [diff] [blame] | 779 | - Memcheck has improved speed and reduced memory use. Run times are |
| 780 | typically reduced by 15-30%, averaging about 24% for SPEC CPU2000. |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 781 | The other tools have smaller but noticeable speed improvments. We |
| 782 | are interested to hear what improvements users get. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 783 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 784 | Memcheck uses less memory due to the introduction of a compressed |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 785 | representation for shadow memory. The space overhead has been |
| 786 | reduced by a factor of up to four, depending on program behaviour. |
| 787 | This means you should be able to run programs that use more memory |
| 788 | than before without hitting problems. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 789 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 790 | - Addrcheck has been removed. It has not worked since version 2.4.0, |
| 791 | and the speed and memory improvements to Memcheck make it redundant. |
| 792 | If you liked using Addrcheck because it didn't give undefined value |
| 793 | errors, you can use the new Memcheck option --undef-value-errors=no |
| 794 | to get the same behaviour. |
| 795 | |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 796 | - The number of undefined-value errors incorrectly reported by |
| 797 | Memcheck has been reduced (such false reports were already very |
| 798 | rare). In particular, efforts have been made to ensure Memcheck |
| 799 | works really well with gcc 4.0/4.1-generated code on X86/Linux and |
| 800 | AMD64/Linux. |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 801 | |
| 802 | - Josef Weidendorfer's popular Callgrind tool has been added. Folding |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 803 | it in was a logical step given its popularity and usefulness, and |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 804 | makes it easier for us to ensure it works "out of the box" on all |
| 805 | supported targets. The associated KDE KCachegrind GUI remains a |
| 806 | separate project. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 807 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 808 | - A new release of the Valkyrie GUI for Memcheck, version 1.2.0, |
| 809 | accompanies this release. Improvements over previous releases |
| 810 | include improved robustness, many refinements to the user interface, |
| 811 | and use of a standard autoconf/automake build system. You can get |
| 812 | it from http://www.valgrind.org/downloads/guis.html. |
| 813 | |
sewardj | 535a235 | 2006-04-18 02:04:52 +0000 | [diff] [blame] | 814 | - Valgrind now works on PPC64/Linux. As with the AMD64/Linux port, |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 815 | this supports programs using to 32G of address space. On 64-bit |
| 816 | capable PPC64/Linux setups, you get a dual architecture build so |
| 817 | that both 32-bit and 64-bit executables can be run. Linux on POWER5 |
| 818 | is supported, and POWER4 is also believed to work. Both 32-bit and |
| 819 | 64-bit DWARF2 is supported. This port is known to work well with |
| 820 | both gcc-compiled and xlc/xlf-compiled code. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 821 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 822 | - Floating point accuracy has been improved for PPC32/Linux. |
| 823 | Specifically, the floating point rounding mode is observed on all FP |
| 824 | arithmetic operations, and multiply-accumulate instructions are |
| 825 | preserved by the compilation pipeline. This means you should get FP |
| 826 | results which are bit-for-bit identical to a native run. These |
| 827 | improvements are also present in the PPC64/Linux port. |
njn | b293916 | 2006-04-18 00:52:37 +0000 | [diff] [blame] | 828 | |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 829 | - Lackey, the example tool, has been improved: |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 830 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 831 | * It has a new option --detailed-counts (off by default) which |
| 832 | causes it to print out a count of loads, stores and ALU operations |
| 833 | done, and their sizes. |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 834 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 835 | * It has a new option --trace-mem (off by default) which causes it |
| 836 | to print out a trace of all memory accesses performed by a |
| 837 | program. It's a good starting point for building Valgrind tools |
| 838 | that need to track memory accesses. Read the comments at the top |
| 839 | of the file lackey/lk_main.c for details. |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 840 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 841 | * The original instrumentation (counting numbers of instructions, |
| 842 | jumps, etc) is now controlled by a new option --basic-counts. It |
| 843 | is on by default. |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 844 | |
| 845 | - MPI support: partial support for debugging distributed applications |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 846 | using the MPI library specification has been added. Valgrind is |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 847 | aware of the memory state changes caused by a subset of the MPI |
| 848 | functions, and will carefully check data passed to the (P)MPI_ |
| 849 | interface. |
| 850 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 851 | - A new flag, --error-exitcode=, has been added. This allows changing |
| 852 | the exit code in runs where Valgrind reported errors, which is |
| 853 | useful when using Valgrind as part of an automated test suite. |
sewardj | b977908 | 2006-05-12 23:50:15 +0000 | [diff] [blame] | 854 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 855 | - Various segfaults when reading old-style "stabs" debug information |
| 856 | have been fixed. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 857 | |
sewardj | c9d09cc | 2006-05-27 03:22:04 +0000 | [diff] [blame] | 858 | - A simple performance evaluation suite has been added. See |
njn | 5359b6f | 2006-06-02 23:57:22 +0000 | [diff] [blame] | 859 | perf/README and README_DEVELOPERS for details. There are |
sewardj | c9d09cc | 2006-05-27 03:22:04 +0000 | [diff] [blame] | 860 | various bells and whistles. |
| 861 | |
sewardj | b70a613 | 2006-05-27 21:14:09 +0000 | [diff] [blame] | 862 | - New configuration flags: |
| 863 | --enable-only32bit |
| 864 | --enable-only64bit |
| 865 | By default, on 64 bit platforms (ppc64-linux, amd64-linux) the build |
| 866 | system will attempt to build a Valgrind which supports both 32-bit |
| 867 | and 64-bit executables. This may not be what you want, and you can |
| 868 | override the default behaviour using these flags. |
| 869 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 870 | Please note that Helgrind is still not working. We have made an |
| 871 | important step towards making it work again, however, with the |
| 872 | addition of function wrapping (see below). |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 873 | |
| 874 | Other user-visible changes: |
| 875 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 876 | - Valgrind now has the ability to intercept and wrap arbitrary |
| 877 | functions. This is a preliminary step towards making Helgrind work |
| 878 | again, and was required for MPI support. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 879 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 880 | - There are some changes to Memcheck's client requests. Some of them |
| 881 | have changed names: |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 882 | |
| 883 | MAKE_NOACCESS --> MAKE_MEM_NOACCESS |
| 884 | MAKE_WRITABLE --> MAKE_MEM_UNDEFINED |
| 885 | MAKE_READABLE --> MAKE_MEM_DEFINED |
| 886 | |
| 887 | CHECK_WRITABLE --> CHECK_MEM_IS_ADDRESSABLE |
| 888 | CHECK_READABLE --> CHECK_MEM_IS_DEFINED |
| 889 | CHECK_DEFINED --> CHECK_VALUE_IS_DEFINED |
| 890 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 891 | The reason for the change is that the old names are subtly |
| 892 | misleading. The old names will still work, but they are deprecated |
| 893 | and may be removed in a future release. |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 894 | |
| 895 | We also added a new client request: |
| 896 | |
| 897 | MAKE_MEM_DEFINED_IF_ADDRESSABLE(a, len) |
| 898 | |
| 899 | which is like MAKE_MEM_DEFINED but only affects a byte if the byte is |
| 900 | already addressable. |
| 901 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 902 | - The way client requests are encoded in the instruction stream has |
| 903 | changed. Unfortunately, this means 3.2.0 will not honour client |
| 904 | requests compiled into binaries using headers from earlier versions |
| 905 | of Valgrind. We will try to keep the client request encodings more |
| 906 | stable in future. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 907 | |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 908 | BUGS FIXED: |
| 909 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 910 | 108258 NPTL pthread cleanup handlers not called |
| 911 | 117290 valgrind is sigKILL'd on startup |
| 912 | 117295 == 117290 |
| 913 | 118703 m_signals.c:1427 Assertion 'tst->status == VgTs_WaitSys' |
| 914 | 118466 add %reg, %reg generates incorrect validity for bit 0 |
| 915 | 123210 New: strlen from ld-linux on amd64 |
| 916 | 123244 DWARF2 CFI reader: unhandled CFI instruction 0:18 |
| 917 | 123248 syscalls in glibc-2.4: openat, fstatat, symlinkat |
| 918 | 123258 socketcall.recvmsg(msg.msg_iov[i] points to uninit |
| 919 | 123535 mremap(new_addr) requires MREMAP_FIXED in 4th arg |
| 920 | 123836 small typo in the doc |
| 921 | 124029 ppc compile failed: `vor' gcc 3.3.5 |
| 922 | 124222 Segfault: @@don't know what type ':' is |
| 923 | 124475 ppc32: crash (syscall?) timer_settime() |
| 924 | 124499 amd64->IR: 0xF 0xE 0x48 0x85 (femms) |
| 925 | 124528 FATAL: aspacem assertion failed: segment_is_sane |
| 926 | 124697 vex x86->IR: 0xF 0x70 0xC9 0x0 (pshufw) |
| 927 | 124892 vex x86->IR: 0xF3 0xAE (REPx SCASB) |
| 928 | 126216 == 124892 |
| 929 | 124808 ppc32: sys_sched_getaffinity() not handled |
| 930 | n-i-bz Very long stabs strings crash m_debuginfo |
| 931 | n-i-bz amd64->IR: 0x66 0xF 0xF5 (pmaddwd) |
| 932 | 125492 ppc32: support a bunch more syscalls |
| 933 | 121617 ppc32/64: coredumping gives assertion failure |
| 934 | 121814 Coregrind return error as exitcode patch |
| 935 | 126517 == 121814 |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 936 | 125607 amd64->IR: 0x66 0xF 0xA3 0x2 (btw etc) |
| 937 | 125651 amd64->IR: 0xF8 0x49 0xFF 0xE3 (clc?) |
| 938 | 126253 x86 movx is wrong |
| 939 | 126451 3.2 SVN doesn't work on ppc32 CPU's without FPU |
| 940 | 126217 increase # threads |
| 941 | 126243 vex x86->IR: popw mem |
| 942 | 126583 amd64->IR: 0x48 0xF 0xA4 0xC2 (shld $1,%rax,%rdx) |
sewardj | b70a613 | 2006-05-27 21:14:09 +0000 | [diff] [blame] | 943 | 126668 amd64->IR: 0x1C 0xFF (sbb $0xff,%al) |
| 944 | 126696 support for CDROMREADRAW ioctl and CDROMREADTOCENTRY fix |
| 945 | 126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624 |
| 946 | 126938 bad checking for syscalls linkat, renameat, symlinkat |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 947 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 948 | (3.2.0RC1: 27 May 2006, vex r1626, valgrind r5947). |
| 949 | (3.2.0: 7 June 2006, vex r1628, valgrind r5957). |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 950 | |
| 951 | |
sewardj | 5065467 | 2006-03-16 11:33:14 +0000 | [diff] [blame] | 952 | Release 3.1.1 (15 March 2006) |
| 953 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 954 | 3.1.1 fixes a bunch of bugs reported in 3.1.0. There is no new |
| 955 | functionality. The fixed bugs are: |
| 956 | |
| 957 | (note: "n-i-bz" means "not in bugzilla" -- this bug does not have |
| 958 | a bugzilla entry). |
| 959 | |
| 960 | n-i-bz ppc32: fsub 3,3,3 in dispatcher doesn't clear NaNs |
| 961 | n-i-bz ppc32: __NR_{set,get}priority |
| 962 | 117332 x86: missing line info with icc 8.1 |
| 963 | 117366 amd64: 0xDD 0x7C fnstsw |
| 964 | 118274 == 117366 |
| 965 | 117367 amd64: 0xD9 0xF4 fxtract |
| 966 | 117369 amd64: __NR_getpriority (140) |
| 967 | 117419 ppc32: lfsu f5, -4(r11) |
| 968 | 117419 ppc32: fsqrt |
| 969 | 117936 more stabs problems (segfaults while reading debug info) |
| 970 | 119914 == 117936 |
| 971 | 120345 == 117936 |
| 972 | 118239 amd64: 0xF 0xAE 0x3F (clflush) |
| 973 | 118939 vm86old system call |
| 974 | n-i-bz memcheck/tests/mempool reads freed memory |
| 975 | n-i-bz AshleyP's custom-allocator assertion |
| 976 | n-i-bz Dirk strict-aliasing stuff |
| 977 | n-i-bz More space for debugger cmd line (Dan Thaler) |
| 978 | n-i-bz Clarified leak checker output message |
| 979 | n-i-bz AshleyP's --gen-suppressions output fix |
| 980 | n-i-bz cg_annotate's --sort option broken |
| 981 | n-i-bz OSet 64-bit fastcmp bug |
| 982 | n-i-bz VG_(getgroups) fix (Shinichi Noda) |
| 983 | n-i-bz ppc32: allocate from callee-saved FP/VMX regs |
| 984 | n-i-bz misaligned path word-size bug in mc_main.c |
| 985 | 119297 Incorrect error message for sse code |
| 986 | 120410 x86: prefetchw (0xF 0xD 0x48 0x4) |
| 987 | 120728 TIOCSERGETLSR, TIOCGICOUNT, HDIO_GET_DMA ioctls |
| 988 | 120658 Build fixes for gcc 2.96 |
| 989 | 120734 x86: Support for changing EIP in signal handler |
| 990 | n-i-bz memcheck/tests/zeropage de-looping fix |
| 991 | n-i-bz x86: fxtract doesn't work reliably |
| 992 | 121662 x86: lock xadd (0xF0 0xF 0xC0 0x2) |
| 993 | 121893 calloc does not always return zeroed memory |
| 994 | 121901 no support for syscall tkill |
| 995 | n-i-bz Suppression update for Debian unstable |
| 996 | 122067 amd64: fcmovnu (0xDB 0xD9) |
| 997 | n-i-bz ppc32: broken signal handling in cpu feature detection |
| 998 | n-i-bz ppc32: rounding mode problems (improved, partial fix only) |
| 999 | 119482 ppc32: mtfsb1 |
| 1000 | n-i-bz ppc32: mtocrf/mfocrf |
| 1001 | |
| 1002 | (3.1.1: 15 March 2006, vex r1597, valgrind r5771). |
| 1003 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1004 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1005 | Release 3.1.0 (25 November 2005) |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1006 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1007 | 3.1.0 is a feature release with a number of significant improvements: |
| 1008 | AMD64 support is much improved, PPC32 support is good enough to be |
| 1009 | usable, and the handling of memory management and address space is |
| 1010 | much more robust. In detail: |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1011 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1012 | - AMD64 support is much improved. The 64-bit vs. 32-bit issues in |
| 1013 | 3.0.X have been resolved, and it should "just work" now in all |
| 1014 | cases. On AMD64 machines both 64-bit and 32-bit versions of |
| 1015 | Valgrind are built. The right version will be invoked |
| 1016 | automatically, even when using --trace-children and mixing execution |
| 1017 | between 64-bit and 32-bit executables. Also, many more instructions |
| 1018 | are supported. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1019 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1020 | - PPC32 support is now good enough to be usable. It should work with |
| 1021 | all tools, but please let us know if you have problems. Three |
| 1022 | classes of CPUs are supported: integer only (no FP, no Altivec), |
| 1023 | which covers embedded PPC uses, integer and FP but no Altivec |
| 1024 | (G3-ish), and CPUs capable of Altivec too (G4, G5). |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1025 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1026 | - Valgrind's address space management has been overhauled. As a |
| 1027 | result, Valgrind should be much more robust with programs that use |
| 1028 | large amounts of memory. There should be many fewer "memory |
| 1029 | exhausted" messages, and debug symbols should be read correctly on |
| 1030 | large (eg. 300MB+) executables. On 32-bit machines the full address |
| 1031 | space available to user programs (usually 3GB or 4GB) can be fully |
| 1032 | utilised. On 64-bit machines up to 32GB of space is usable; when |
| 1033 | using Memcheck that means your program can use up to about 14GB. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1034 | |
| 1035 | A side effect of this change is that Valgrind is no longer protected |
| 1036 | against wild writes by the client. This feature was nice but relied |
| 1037 | on the x86 segment registers and so wasn't portable. |
| 1038 | |
| 1039 | - Most users should not notice, but as part of the address space |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1040 | manager change, the way Valgrind is built has been changed. Each |
| 1041 | tool is now built as a statically linked stand-alone executable, |
| 1042 | rather than as a shared object that is dynamically linked with the |
| 1043 | core. The "valgrind" program invokes the appropriate tool depending |
| 1044 | on the --tool option. This slightly increases the amount of disk |
| 1045 | space used by Valgrind, but it greatly simplified many things and |
| 1046 | removed Valgrind's dependence on glibc. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1047 | |
njn | 336c89d | 2005-11-20 18:14:04 +0000 | [diff] [blame] | 1048 | Please note that Addrcheck and Helgrind are still not working. Work |
| 1049 | is underway to reinstate them (or equivalents). We apologise for the |
| 1050 | inconvenience. |
| 1051 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1052 | Other user-visible changes: |
| 1053 | |
| 1054 | - The --weird-hacks option has been renamed --sim-hints. |
| 1055 | |
| 1056 | - The --time-stamp option no longer gives an absolute date and time. |
| 1057 | It now prints the time elapsed since the program began. |
| 1058 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1059 | - It should build with gcc-2.96. |
| 1060 | |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 1061 | - Valgrind can now run itself (see README_DEVELOPERS for how). |
sewardj | 4705861 | 2005-11-16 19:13:13 +0000 | [diff] [blame] | 1062 | This is not much use to you, but it means the developers can now |
| 1063 | profile Valgrind using Cachegrind. As a result a couple of |
| 1064 | performance bad cases have been fixed. |
| 1065 | |
sewardj | 6a5a69c | 2005-11-17 00:51:36 +0000 | [diff] [blame] | 1066 | - The XML output format has changed slightly. See |
| 1067 | docs/internals/xml-output.txt. |
| 1068 | |
njn | 14c9add | 2005-11-18 17:36:01 +0000 | [diff] [blame] | 1069 | - Core dumping has been reinstated (it was disabled in 3.0.0 and 3.0.1). |
| 1070 | If your program crashes while running under Valgrind, a core file with |
| 1071 | the name "vgcore.<pid>" will be created (if your settings allow core |
| 1072 | file creation). Note that the floating point information is not all |
| 1073 | there. If Valgrind itself crashes, the OS will create a normal core |
| 1074 | file. |
| 1075 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1076 | The following are some user-visible changes that occurred in earlier |
| 1077 | versions that may not have been announced, or were announced but not |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 1078 | widely noticed. So we're mentioning them now. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1079 | |
| 1080 | - The --tool flag is optional once again; if you omit it, Memcheck |
| 1081 | is run by default. |
| 1082 | |
| 1083 | - The --num-callers flag now has a default value of 12. It was |
| 1084 | previously 4. |
| 1085 | |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 1086 | - The --xml=yes flag causes Valgrind's output to be produced in XML |
| 1087 | format. This is designed to make it easy for other programs to |
| 1088 | consume Valgrind's output. The format is described in the file |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1089 | docs/internals/xml-format.txt. |
| 1090 | |
njn | 1f50399 | 2005-11-13 16:41:15 +0000 | [diff] [blame] | 1091 | - The --gen-suppressions flag supports an "all" value that causes every |
| 1092 | suppression to be printed without asking. |
| 1093 | |
njn | ee88d28 | 2005-11-20 17:19:28 +0000 | [diff] [blame] | 1094 | - The --log-file option no longer puts "pid" in the filename, eg. the |
| 1095 | old name "foo.pid12345" is now "foo.12345". |
| 1096 | |
njn | c66077e | 2005-11-20 18:02:15 +0000 | [diff] [blame] | 1097 | - There are several graphical front-ends for Valgrind, such as Valkyrie, |
| 1098 | Alleyoop and Valgui. See http://www.valgrind.org/downloads/guis.html |
| 1099 | for a list. |
| 1100 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1101 | BUGS FIXED: |
| 1102 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 1103 | 109861 amd64 hangs at startup |
| 1104 | 110301 ditto |
| 1105 | 111554 valgrind crashes with Cannot allocate memory |
| 1106 | 111809 Memcheck tool doesn't start java |
| 1107 | 111901 cross-platform run of cachegrind fails on opteron |
| 1108 | 113468 (vgPlain_mprotect_range): Assertion 'r != -1' failed. |
| 1109 | 92071 Reading debugging info uses too much memory |
| 1110 | 109744 memcheck loses track of mmap from direct ld-linux.so.2 |
| 1111 | 110183 tail of page with _end |
| 1112 | 82301 FV memory layout too rigid |
| 1113 | 98278 Infinite recursion possible when allocating memory |
| 1114 | 108994 Valgrind runs out of memory due to 133x overhead |
| 1115 | 115643 valgrind cannot allocate memory |
| 1116 | 105974 vg_hashtable.c static hash table |
| 1117 | 109323 ppc32: dispatch.S uses Altivec insn, which doesn't work on POWER. |
| 1118 | 109345 ptrace_setregs not yet implemented for ppc |
| 1119 | 110831 Would like to be able to run against both 32 and 64 bit |
| 1120 | binaries on AMD64 |
| 1121 | 110829 == 110831 |
| 1122 | 111781 compile of valgrind-3.0.0 fails on my linux (gcc 2.X prob) |
| 1123 | 112670 Cachegrind: cg_main.c:486 (handleOneStatement ... |
| 1124 | 112941 vex x86: 0xD9 0xF4 (fxtract) |
| 1125 | 110201 == 112941 |
| 1126 | 113015 vex amd64->IR: 0xE3 0x14 0x48 0x83 (jrcxz) |
| 1127 | 113126 Crash with binaries built with -gstabs+/-ggdb |
| 1128 | 104065 == 113126 |
| 1129 | 115741 == 113126 |
| 1130 | 113403 Partial SSE3 support on x86 |
| 1131 | 113541 vex: Grp5(x86) (alt encoding inc/dec) case 1 |
| 1132 | 113642 valgrind crashes when trying to read debug information |
| 1133 | 113810 vex x86->IR: 66 0F F6 (66 + PSADBW == SSE PSADBW) |
| 1134 | 113796 read() and write() do not work if buffer is in shared memory |
| 1135 | 113851 vex x86->IR: (pmaddwd): 0x66 0xF 0xF5 0xC7 |
| 1136 | 114366 vex amd64 cannnot handle __asm__( "fninit" ) |
| 1137 | 114412 vex amd64->IR: 0xF 0xAD 0xC2 0xD3 (128-bit shift, shrdq?) |
| 1138 | 114455 vex amd64->IR: 0xF 0xAC 0xD0 0x1 (also shrdq) |
| 1139 | 115590: amd64->IR: 0x67 0xE3 0x9 0xEB (address size override) |
| 1140 | 115953 valgrind svn r5042 does not build with parallel make (-j3) |
| 1141 | 116057 maximum instruction size - VG_MAX_INSTR_SZB too small? |
| 1142 | 116483 shmat failes with invalid argument |
| 1143 | 102202 valgrind crashes when realloc'ing until out of memory |
| 1144 | 109487 == 102202 |
| 1145 | 110536 == 102202 |
| 1146 | 112687 == 102202 |
| 1147 | 111724 vex amd64->IR: 0x41 0xF 0xAB (more BT{,S,R,C} fun n games) |
| 1148 | 111748 vex amd64->IR: 0xDD 0xE2 (fucom) |
| 1149 | 111785 make fails if CC contains spaces |
| 1150 | 111829 vex x86->IR: sbb AL, Ib |
| 1151 | 111851 vex x86->IR: 0x9F 0x89 (lahf/sahf) |
| 1152 | 112031 iopl on AMD64 and README_MISSING_SYSCALL_OR_IOCTL update |
| 1153 | 112152 code generation for Xin_MFence on x86 with SSE0 subarch |
| 1154 | 112167 == 112152 |
| 1155 | 112789 == 112152 |
| 1156 | 112199 naked ar tool is used in vex makefile |
| 1157 | 112501 vex x86->IR: movq (0xF 0x7F 0xC1 0xF) (mmx MOVQ) |
| 1158 | 113583 == 112501 |
| 1159 | 112538 memalign crash |
| 1160 | 113190 Broken links in docs/html/ |
| 1161 | 113230 Valgrind sys_pipe on x86-64 wrongly thinks file descriptors |
| 1162 | should be 64bit |
| 1163 | 113996 vex amd64->IR: fucomp (0xDD 0xE9) |
| 1164 | 114196 vex x86->IR: out %eax,(%dx) (0xEF 0xC9 0xC3 0x90) |
| 1165 | 114289 Memcheck fails to intercept malloc when used in an uclibc environment |
| 1166 | 114756 mbind syscall support |
| 1167 | 114757 Valgrind dies with assertion: Assertion 'noLargerThan > 0' failed |
| 1168 | 114563 stack tracking module not informed when valgrind switches threads |
| 1169 | 114564 clone() and stacks |
| 1170 | 114565 == 114564 |
| 1171 | 115496 glibc crashes trying to use sysinfo page |
| 1172 | 116200 enable fsetxattr, fgetxattr, and fremovexattr for amd64 |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1173 | |
sewardj | ae17e7e | 2005-11-20 19:45:30 +0000 | [diff] [blame] | 1174 | (3.1.0RC1: 20 November 2005, vex r1466, valgrind r5224). |
sewardj | fa46202 | 2005-11-26 13:38:58 +0000 | [diff] [blame] | 1175 | (3.1.0: 26 November 2005, vex r1471, valgrind r5235). |
sewardj | ae17e7e | 2005-11-20 19:45:30 +0000 | [diff] [blame] | 1176 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 1177 | |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 1178 | Release 3.0.1 (29 August 2005) |
| 1179 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1180 | 3.0.1 fixes a bunch of bugs reported in 3.0.0. There is no new |
| 1181 | functionality. Some of the fixed bugs are critical, so if you |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 1182 | use/distribute 3.0.0, an upgrade to 3.0.1 is recommended. The fixed |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 1183 | bugs are: |
| 1184 | |
| 1185 | (note: "n-i-bz" means "not in bugzilla" -- this bug does not have |
| 1186 | a bugzilla entry). |
| 1187 | |
| 1188 | 109313 (== 110505) x86 cmpxchg8b |
| 1189 | n-i-bz x86: track but ignore changes to %eflags.AC (alignment check) |
| 1190 | 110102 dis_op2_E_G(amd64) |
| 1191 | 110202 x86 sys_waitpid(#286) |
| 1192 | 110203 clock_getres(,0) |
| 1193 | 110208 execve fail wrong retval |
| 1194 | 110274 SSE1 now mandatory for x86 |
| 1195 | 110388 amd64 0xDD 0xD1 |
| 1196 | 110464 amd64 0xDC 0x1D FCOMP |
| 1197 | 110478 amd64 0xF 0xD PREFETCH |
| 1198 | n-i-bz XML <unique> printing wrong |
| 1199 | n-i-bz Dirk r4359 (amd64 syscalls from trunk) |
| 1200 | 110591 amd64 and x86: rdtsc not implemented properly |
| 1201 | n-i-bz Nick r4384 (stub implementations of Addrcheck and Helgrind) |
| 1202 | 110652 AMD64 valgrind crashes on cwtd instruction |
| 1203 | 110653 AMD64 valgrind crashes on sarb $0x4,foo(%rip) instruction |
| 1204 | 110656 PATH=/usr/bin::/bin valgrind foobar stats ./fooba |
| 1205 | 110657 Small test fixes |
| 1206 | 110671 vex x86->IR: unhandled instruction bytes: 0xF3 0xC3 (rep ret) |
| 1207 | n-i-bz Nick (Cachegrind should not assert when it encounters a client |
| 1208 | request.) |
| 1209 | 110685 amd64->IR: unhandled instruction bytes: 0xE1 0x56 (loope Jb) |
| 1210 | 110830 configuring with --host fails to build 32 bit on 64 bit target |
| 1211 | 110875 Assertion when execve fails |
| 1212 | n-i-bz Updates to Memcheck manual |
| 1213 | n-i-bz Fixed broken malloc_usable_size() |
| 1214 | 110898 opteron instructions missing: btq btsq btrq bsfq |
| 1215 | 110954 x86->IR: unhandled instruction bytes: 0xE2 0xF6 (loop Jb) |
| 1216 | n-i-bz Make suppressions work for "???" lines in stacktraces. |
| 1217 | 111006 bogus warnings from linuxthreads |
| 1218 | 111092 x86: dis_Grp2(Reg): unhandled case(x86) |
| 1219 | 111231 sctp_getladdrs() and sctp_getpaddrs() returns uninitialized |
| 1220 | memory |
| 1221 | 111102 (comment #4) Fixed 64-bit unclean "silly arg" message |
| 1222 | n-i-bz vex x86->IR: unhandled instruction bytes: 0x14 0x0 |
| 1223 | n-i-bz minor umount/fcntl wrapper fixes |
| 1224 | 111090 Internal Error running Massif |
| 1225 | 101204 noisy warning |
| 1226 | 111513 Illegal opcode for SSE instruction (x86 movups) |
| 1227 | 111555 VEX/Makefile: CC is set to gcc |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 1228 | n-i-bz Fix XML bugs in FAQ |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 1229 | |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 1230 | (3.0.1: 29 August 05, |
| 1231 | vex/branches/VEX_3_0_BRANCH r1367, |
| 1232 | valgrind/branches/VALGRIND_3_0_BRANCH r4574). |
sewardj | 820c772 | 2005-08-29 13:44:43 +0000 | [diff] [blame] | 1233 | |
| 1234 | |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 1235 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 1236 | Release 3.0.0 (3 August 2005) |
| 1237 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 1238 | 3.0.0 is a major overhaul of Valgrind. The most significant user |
| 1239 | visible change is that Valgrind now supports architectures other than |
| 1240 | x86. The new architectures it supports are AMD64 and PPC32, and the |
| 1241 | infrastructure is present for other architectures to be added later. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1242 | |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 1243 | AMD64 support works well, but has some shortcomings: |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1244 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1245 | - It generally won't be as solid as the x86 version. For example, |
| 1246 | support for more obscure instructions and system calls may be missing. |
| 1247 | We will fix these as they arise. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1248 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1249 | - Address space may be limited; see the point about |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1250 | position-independent executables below. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1251 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1252 | - If Valgrind is built on an AMD64 machine, it will only run 64-bit |
| 1253 | executables. If you want to run 32-bit x86 executables under Valgrind |
| 1254 | on an AMD64, you will need to build Valgrind on an x86 machine and |
| 1255 | copy it to the AMD64 machine. And it probably won't work if you do |
| 1256 | something tricky like exec'ing a 32-bit program from a 64-bit program |
| 1257 | while using --trace-children=yes. We hope to improve this situation |
| 1258 | in the future. |
| 1259 | |
| 1260 | The PPC32 support is very basic. It may not work reliably even for |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1261 | small programs, but it's a start. Many thanks to Paul Mackerras for |
| 1262 | his great work that enabled this support. We are working to make |
| 1263 | PPC32 usable as soon as possible. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1264 | |
| 1265 | Other user-visible changes: |
| 1266 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 1267 | - Valgrind is no longer built by default as a position-independent |
| 1268 | executable (PIE), as this caused too many problems. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1269 | |
| 1270 | Without PIE enabled, AMD64 programs will only be able to access 2GB of |
| 1271 | address space. We will fix this eventually, but not for the moment. |
| 1272 | |
| 1273 | Use --enable-pie at configure-time to turn this on. |
| 1274 | |
| 1275 | - Support for programs that use stack-switching has been improved. Use |
| 1276 | the --max-stackframe flag for simple cases, and the |
| 1277 | VALGRIND_STACK_REGISTER, VALGRIND_STACK_DEREGISTER and |
| 1278 | VALGRIND_STACK_CHANGE client requests for trickier cases. |
| 1279 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1280 | - Support for programs that use self-modifying code has been improved, |
| 1281 | in particular programs that put temporary code fragments on the stack. |
| 1282 | This helps for C programs compiled with GCC that use nested functions, |
njn | e772332 | 2005-07-24 17:19:09 +0000 | [diff] [blame] | 1283 | and also Ada programs. This is controlled with the --smc-check |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1284 | flag, although the default setting should work in most cases. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1285 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1286 | - Output can now be printed in XML format. This should make it easier |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1287 | for tools such as GUI front-ends and automated error-processing |
| 1288 | schemes to use Valgrind output as input. The --xml flag controls this. |
| 1289 | As part of this change, ELF directory information is read from executables, |
| 1290 | so absolute source file paths are available if needed. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1291 | |
| 1292 | - Programs that allocate many heap blocks may run faster, due to |
| 1293 | improvements in certain data structures. |
| 1294 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 1295 | - Addrcheck is currently not working. We hope to get it working again |
| 1296 | soon. Helgrind is still not working, as was the case for the 2.4.0 |
| 1297 | release. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1298 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1299 | - The JITter has been completely rewritten, and is now in a separate |
| 1300 | library, called Vex. This enabled a lot of the user-visible changes, |
| 1301 | such as new architecture support. The new JIT unfortunately translates |
| 1302 | more slowly than the old one, so programs may take longer to start. |
| 1303 | We believe the code quality is produces is about the same, so once |
| 1304 | started, programs should run at about the same speed. Feedback about |
| 1305 | this would be useful. |
| 1306 | |
| 1307 | On the plus side, Vex and hence Memcheck tracks value flow properly |
| 1308 | through floating point and vector registers, something the 2.X line |
| 1309 | could not do. That means that Memcheck is much more likely to be |
| 1310 | usably accurate on vectorised code. |
| 1311 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 1312 | - There is a subtle change to the way exiting of threaded programs |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1313 | is handled. In 3.0, Valgrind's final diagnostic output (leak check, |
| 1314 | etc) is not printed until the last thread exits. If the last thread |
| 1315 | to exit was not the original thread which started the program, any |
| 1316 | other process wait()-ing on this one to exit may conclude it has |
| 1317 | finished before the diagnostic output is printed. This may not be |
| 1318 | what you expect. 2.X had a different scheme which avoided this |
| 1319 | problem, but caused deadlocks under obscure circumstances, so we |
| 1320 | are trying something different for 3.0. |
| 1321 | |
| 1322 | - Small changes in control log file naming which make it easier to |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 1323 | use valgrind for debugging MPI-based programs. The relevant |
| 1324 | new flags are --log-file-exactly= and --log-file-qualifier=. |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1325 | |
| 1326 | - As part of adding AMD64 support, DWARF2 CFI-based stack unwinding |
| 1327 | support was added. In principle this means Valgrind can produce |
| 1328 | meaningful backtraces on x86 code compiled with -fomit-frame-pointer |
tom | 81868f0 | 2005-07-27 10:33:08 +0000 | [diff] [blame] | 1329 | providing you also compile your code with -fasynchronous-unwind-tables. |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1330 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 1331 | - The documentation build system has been completely redone. |
| 1332 | The documentation masters are now in XML format, and from that |
| 1333 | HTML, PostScript and PDF documentation is generated. As a result |
| 1334 | the manual is now available in book form. Note that the |
| 1335 | documentation in the source tarballs is pre-built, so you don't need |
| 1336 | any XML processing tools to build Valgrind from a tarball. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1337 | |
| 1338 | Changes that are not user-visible: |
| 1339 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 1340 | - The code has been massively overhauled in order to modularise it. |
| 1341 | As a result we hope it is easier to navigate and understand. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1342 | |
| 1343 | - Lots of code has been rewritten. |
| 1344 | |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 1345 | BUGS FIXED: |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1346 | |
sewardj | 79bd9b6 | 2005-08-03 16:40:10 +0000 | [diff] [blame] | 1347 | 110046 sz == 4 assertion failed |
| 1348 | 109810 vex amd64->IR: unhandled instruction bytes: 0xA3 0x4C 0x70 0xD7 |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 1349 | 109802 Add a plausible_stack_size command-line parameter ? |
| 1350 | 109783 unhandled ioctl TIOCMGET (running hw detection tool discover) |
| 1351 | 109780 unhandled ioctl BLKSSZGET (running fdisk -l /dev/hda) |
| 1352 | 109718 vex x86->IR: unhandled instruction: ffreep |
| 1353 | 109429 AMD64 unhandled syscall: 127 (sigpending) |
| 1354 | 109401 false positive uninit in strchr from ld-linux.so.2 |
| 1355 | 109385 "stabs" parse failure |
| 1356 | 109378 amd64: unhandled instruction REP NOP |
| 1357 | 109376 amd64: unhandled instruction LOOP Jb |
| 1358 | 109363 AMD64 unhandled instruction bytes |
| 1359 | 109362 AMD64 unhandled syscall: 24 (sched_yield) |
| 1360 | 109358 fork() won't work with valgrind-3.0 SVN |
| 1361 | 109332 amd64 unhandled instruction: ADC Ev, Gv |
| 1362 | 109314 Bogus memcheck report on amd64 |
| 1363 | 108883 Crash; vg_memory.c:905 (vgPlain_init_shadow_range): |
| 1364 | Assertion `vgPlain_defined_init_shadow_page()' failed. |
| 1365 | 108349 mincore syscall parameter checked incorrectly |
| 1366 | 108059 build infrastructure: small update |
| 1367 | 107524 epoll_ctl event parameter checked on EPOLL_CTL_DEL |
| 1368 | 107123 Vex dies with unhandled instructions: 0xD9 0x31 0xF 0xAE |
| 1369 | 106841 auxmap & openGL problems |
| 1370 | 106713 SDL_Init causes valgrind to exit |
| 1371 | 106352 setcontext and makecontext not handled correctly |
| 1372 | 106293 addresses beyond initial client stack allocation |
| 1373 | not checked in VALGRIND_DO_LEAK_CHECK |
| 1374 | 106283 PIE client programs are loaded at address 0 |
| 1375 | 105831 Assertion `vgPlain_defined_init_shadow_page()' failed. |
| 1376 | 105039 long run-times probably due to memory manager |
| 1377 | 104797 valgrind needs to be aware of BLKGETSIZE64 |
| 1378 | 103594 unhandled instruction: FICOM |
| 1379 | 103320 Valgrind 2.4.0 fails to compile with gcc 3.4.3 and -O0 |
| 1380 | 103168 potentially memory leak in coregrind/ume.c |
| 1381 | 102039 bad permissions for mapped region at address 0xB7C73680 |
| 1382 | 101881 weird assertion problem |
| 1383 | 101543 Support fadvise64 syscalls |
| 1384 | 75247 x86_64/amd64 support (the biggest "bug" we have ever fixed) |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 1385 | |
sewardj | 9a91951 | 2005-08-03 17:01:51 +0000 | [diff] [blame] | 1386 | (3.0RC1: 27 July 05, vex r1303, valgrind r4283). |
sewardj | 1346e13 | 2005-08-03 20:42:06 +0000 | [diff] [blame] | 1387 | (3.0.0: 3 August 05, vex r1313, valgrind r4316). |
sewardj | bfa2b99 | 2005-07-27 17:49:17 +0000 | [diff] [blame] | 1388 | |
| 1389 | |
| 1390 | |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1391 | Stable release 2.4.0 (March 2005) -- CHANGES RELATIVE TO 2.2.0 |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1392 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1393 | 2.4.0 brings many significant changes and bug fixes. The most |
| 1394 | significant user-visible change is that we no longer supply our own |
| 1395 | pthread implementation. Instead, Valgrind is finally capable of |
| 1396 | running the native thread library, either LinuxThreads or NPTL. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1397 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1398 | This means our libpthread has gone, along with the bugs associated |
| 1399 | with it. Valgrind now supports the kernel's threading syscalls, and |
| 1400 | lets you use your standard system libpthread. As a result: |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1401 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1402 | * There are many fewer system dependencies and strange library-related |
| 1403 | bugs. There is a small performance improvement, and a large |
| 1404 | stability improvement. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1405 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1406 | * On the downside, Valgrind can no longer report misuses of the POSIX |
| 1407 | PThreads API. It also means that Helgrind currently does not work. |
| 1408 | We hope to fix these problems in a future release. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1409 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1410 | Note that running the native thread libraries does not mean Valgrind |
| 1411 | is able to provide genuine concurrent execution on SMPs. We still |
| 1412 | impose the restriction that only one thread is running at any given |
| 1413 | time. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1414 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1415 | There are many other significant changes too: |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1416 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1417 | * Memcheck is (once again) the default tool. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1418 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1419 | * The default stack backtrace is now 12 call frames, rather than 4. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1420 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1421 | * Suppressions can have up to 25 call frame matches, rather than 4. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1422 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1423 | * Memcheck and Addrcheck use less memory. Under some circumstances, |
| 1424 | they no longer allocate shadow memory if there are large regions of |
| 1425 | memory with the same A/V states - such as an mmaped file. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1426 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1427 | * The memory-leak detector in Memcheck and Addrcheck has been |
| 1428 | improved. It now reports more types of memory leak, including |
| 1429 | leaked cycles. When reporting leaked memory, it can distinguish |
| 1430 | between directly leaked memory (memory with no references), and |
| 1431 | indirectly leaked memory (memory only referred to by other leaked |
| 1432 | memory). |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1433 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1434 | * Memcheck's confusion over the effect of mprotect() has been fixed: |
| 1435 | previously mprotect could erroneously mark undefined data as |
| 1436 | defined. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1437 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1438 | * Signal handling is much improved and should be very close to what |
| 1439 | you get when running natively. |
| 1440 | |
| 1441 | One result of this is that Valgrind observes changes to sigcontexts |
| 1442 | passed to signal handlers. Such modifications will take effect when |
| 1443 | the signal returns. You will need to run with --single-step=yes to |
| 1444 | make this useful. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1445 | |
| 1446 | * Valgrind is built in Position Independent Executable (PIE) format if |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1447 | your toolchain supports it. This allows it to take advantage of all |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1448 | the available address space on systems with 4Gbyte user address |
| 1449 | spaces. |
| 1450 | |
| 1451 | * Valgrind can now run itself (requires PIE support). |
| 1452 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1453 | * Syscall arguments are now checked for validity. Previously all |
| 1454 | memory used by syscalls was checked, but now the actual values |
| 1455 | passed are also checked. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1456 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1457 | * Syscall wrappers are more robust against bad addresses being passed |
| 1458 | to syscalls: they will fail with EFAULT rather than killing Valgrind |
| 1459 | with SIGSEGV. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1460 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 1461 | * Because clone() is directly supported, some non-pthread uses of it |
| 1462 | will work. Partial sharing (where some resources are shared, and |
| 1463 | some are not) is not supported. |
| 1464 | |
| 1465 | * open() and readlink() on /proc/self/exe are supported. |
| 1466 | |
| 1467 | BUGS FIXED: |
| 1468 | |
| 1469 | 88520 pipe+fork+dup2 kills the main program |
| 1470 | 88604 Valgrind Aborts when using $VALGRIND_OPTS and user progra... |
| 1471 | 88614 valgrind: vg_libpthread.c:2323 (read): Assertion `read_pt... |
| 1472 | 88703 Stabs parser fails to handle ";" |
| 1473 | 88886 ioctl wrappers for TIOCMBIS and TIOCMBIC |
| 1474 | 89032 valgrind pthread_cond_timedwait fails |
| 1475 | 89106 the 'impossible' happened |
| 1476 | 89139 Missing sched_setaffinity & sched_getaffinity |
| 1477 | 89198 valgrind lacks support for SIOCSPGRP and SIOCGPGRP |
| 1478 | 89263 Missing ioctl translations for scsi-generic and CD playing |
| 1479 | 89440 tests/deadlock.c line endings |
| 1480 | 89481 `impossible' happened: EXEC FAILED |
| 1481 | 89663 valgrind 2.2.0 crash on Redhat 7.2 |
| 1482 | 89792 Report pthread_mutex_lock() deadlocks instead of returnin... |
| 1483 | 90111 statvfs64 gives invalid error/warning |
| 1484 | 90128 crash+memory fault with stabs generated by gnat for a run... |
| 1485 | 90778 VALGRIND_CHECK_DEFINED() not as documented in memcheck.h |
| 1486 | 90834 cachegrind crashes at end of program without reporting re... |
| 1487 | 91028 valgrind: vg_memory.c:229 (vgPlain_unmap_range): Assertio... |
| 1488 | 91162 valgrind crash while debugging drivel 1.2.1 |
| 1489 | 91199 Unimplemented function |
| 1490 | 91325 Signal routing does not propagate the siginfo structure |
| 1491 | 91599 Assertion `cv == ((void *)0)' |
| 1492 | 91604 rw_lookup clears orig and sends the NULL value to rw_new |
| 1493 | 91821 Small problems building valgrind with $top_builddir ne $t... |
| 1494 | 91844 signal 11 (SIGSEGV) at get_tcb (libpthread.c:86) in corec... |
| 1495 | 92264 UNIMPLEMENTED FUNCTION: pthread_condattr_setpshared |
| 1496 | 92331 per-target flags necessitate AM_PROG_CC_C_O |
| 1497 | 92420 valgrind doesn't compile with linux 2.6.8.1/9 |
| 1498 | 92513 Valgrind 2.2.0 generates some warning messages |
| 1499 | 92528 vg_symtab2.c:170 (addLoc): Assertion `loc->size > 0' failed. |
| 1500 | 93096 unhandled ioctl 0x4B3A and 0x5601 |
| 1501 | 93117 Tool and core interface versions do not match |
| 1502 | 93128 Can't run valgrind --tool=memcheck because of unimplement... |
| 1503 | 93174 Valgrind can crash if passed bad args to certain syscalls |
| 1504 | 93309 Stack frame in new thread is badly aligned |
| 1505 | 93328 Wrong types used with sys_sigprocmask() |
| 1506 | 93763 /usr/include/asm/msr.h is missing |
| 1507 | 93776 valgrind: vg_memory.c:508 (vgPlain_find_map_space): Asser... |
| 1508 | 93810 fcntl() argument checking a bit too strict |
| 1509 | 94378 Assertion `tst->sigqueue_head != tst->sigqueue_tail' failed. |
| 1510 | 94429 valgrind 2.2.0 segfault with mmap64 in glibc 2.3.3 |
| 1511 | 94645 Impossible happened: PINSRW mem |
| 1512 | 94953 valgrind: the `impossible' happened: SIGSEGV |
| 1513 | 95667 Valgrind does not work with any KDE app |
| 1514 | 96243 Assertion 'res==0' failed |
| 1515 | 96252 stage2 loader of valgrind fails to allocate memory |
| 1516 | 96520 All programs crashing at _dl_start (in /lib/ld-2.3.3.so) ... |
| 1517 | 96660 ioctl CDROMREADTOCENTRY causes bogus warnings |
| 1518 | 96747 After looping in a segfault handler, the impossible happens |
| 1519 | 96923 Zero sized arrays crash valgrind trace back with SIGFPE |
| 1520 | 96948 valgrind stops with assertion failure regarding mmap2 |
| 1521 | 96966 valgrind fails when application opens more than 16 sockets |
| 1522 | 97398 valgrind: vg_libpthread.c:2667 Assertion failed |
| 1523 | 97407 valgrind: vg_mylibc.c:1226 (vgPlain_safe_fd): Assertion `... |
| 1524 | 97427 "Warning: invalid file descriptor -1 in syscall close()" ... |
| 1525 | 97785 missing backtrace |
| 1526 | 97792 build in obj dir fails - autoconf / makefile cleanup |
| 1527 | 97880 pthread_mutex_lock fails from shared library (special ker... |
| 1528 | 97975 program aborts without ang VG messages |
| 1529 | 98129 Failed when open and close file 230000 times using stdio |
| 1530 | 98175 Crashes when using valgrind-2.2.0 with a program using al... |
| 1531 | 98288 Massif broken |
| 1532 | 98303 UNIMPLEMENTED FUNCTION pthread_condattr_setpshared |
| 1533 | 98630 failed--compilation missing warnings.pm, fails to make he... |
| 1534 | 98756 Cannot valgrind signal-heavy kdrive X server |
| 1535 | 98966 valgrinding the JVM fails with a sanity check assertion |
| 1536 | 99035 Valgrind crashes while profiling |
| 1537 | 99142 loops with message "Signal 11 being dropped from thread 0... |
| 1538 | 99195 threaded apps crash on thread start (using QThread::start... |
| 1539 | 99348 Assertion `vgPlain_lseek(core_fd, 0, 1) == phdrs[i].p_off... |
| 1540 | 99568 False negative due to mishandling of mprotect |
| 1541 | 99738 valgrind memcheck crashes on program that uses sigitimer |
| 1542 | 99923 0-sized allocations are reported as leaks |
| 1543 | 99949 program seg faults after exit() |
| 1544 | 100036 "newSuperblock's request for 1048576 bytes failed" |
| 1545 | 100116 valgrind: (pthread_cond_init): Assertion `sizeof(* cond) ... |
| 1546 | 100486 memcheck reports "valgrind: the `impossible' happened: V... |
| 1547 | 100833 second call to "mremap" fails with EINVAL |
| 1548 | 101156 (vgPlain_find_map_space): Assertion `(addr & ((1 << 12)-1... |
| 1549 | 101173 Assertion `recDepth >= 0 && recDepth < 500' failed |
| 1550 | 101291 creating threads in a forked process fails |
| 1551 | 101313 valgrind causes different behavior when resizing a window... |
| 1552 | 101423 segfault for c++ array of floats |
| 1553 | 101562 valgrind massif dies on SIGINT even with signal handler r... |
| 1554 | |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 1555 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1556 | Stable release 2.2.0 (31 August 2004) -- CHANGES RELATIVE TO 2.0.0 |
| 1557 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
jseward | 7d180d9 | 2004-08-30 18:15:37 +0000 | [diff] [blame] | 1558 | 2.2.0 brings nine months worth of improvements and bug fixes. We |
| 1559 | believe it to be a worthy successor to 2.0.0. There are literally |
| 1560 | hundreds of bug fixes and minor improvements. There are also some |
| 1561 | fairly major user-visible changes: |
| 1562 | |
| 1563 | * A complete overhaul of handling of system calls and signals, and |
| 1564 | their interaction with threads. In general, the accuracy of the |
| 1565 | system call, thread and signal simulations is much improved: |
| 1566 | |
| 1567 | - Blocking system calls behave exactly as they do when running |
| 1568 | natively (not on valgrind). That is, if a syscall blocks only the |
| 1569 | calling thread when running natively, than it behaves the same on |
| 1570 | valgrind. No more mysterious hangs because V doesn't know that some |
| 1571 | syscall or other, should block only the calling thread. |
| 1572 | |
| 1573 | - Interrupted syscalls should now give more faithful results. |
| 1574 | |
| 1575 | - Signal contexts in signal handlers are supported. |
| 1576 | |
| 1577 | * Improvements to NPTL support to the extent that V now works |
| 1578 | properly on NPTL-only setups. |
| 1579 | |
| 1580 | * Greater isolation between Valgrind and the program being run, so |
| 1581 | the program is less likely to inadvertently kill Valgrind by |
| 1582 | doing wild writes. |
| 1583 | |
| 1584 | * Massif: a new space profiling tool. Try it! It's cool, and it'll |
| 1585 | tell you in detail where and when your C/C++ code is allocating heap. |
| 1586 | Draws pretty .ps pictures of memory use against time. A potentially |
| 1587 | powerful tool for making sense of your program's space use. |
| 1588 | |
| 1589 | * File descriptor leakage checks. When enabled, Valgrind will print out |
| 1590 | a list of open file descriptors on exit. |
| 1591 | |
| 1592 | * Improved SSE2/SSE3 support. |
| 1593 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1594 | * Time-stamped output; use --time-stamp=yes |
| 1595 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1596 | |
| 1597 | |
| 1598 | Stable release 2.2.0 (31 August 2004) -- CHANGES RELATIVE TO 2.1.2 |
| 1599 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1600 | 2.2.0 is not much different from 2.1.2, released seven weeks ago. |
| 1601 | A number of bugs have been fixed, most notably #85658, which gave |
| 1602 | problems for quite a few people. There have been many internal |
| 1603 | cleanups, but those are not user visible. |
| 1604 | |
| 1605 | The following bugs have been fixed since 2.1.2: |
| 1606 | |
| 1607 | 85658 Assert in coregrind/vg_libpthread.c:2326 (open64) != |
| 1608 | (void*)0 failed |
| 1609 | This bug was reported multiple times, and so the following |
| 1610 | duplicates of it are also fixed: 87620, 85796, 85935, 86065, |
| 1611 | 86919, 86988, 87917, 88156 |
| 1612 | |
| 1613 | 80716 Semaphore mapping bug caused by unmap (sem_destroy) |
| 1614 | (Was fixed prior to 2.1.2) |
| 1615 | |
| 1616 | 86987 semctl and shmctl syscalls family is not handled properly |
| 1617 | |
| 1618 | 86696 valgrind 2.1.2 + RH AS2.1 + librt |
| 1619 | |
| 1620 | 86730 valgrind locks up at end of run with assertion failure |
| 1621 | in __pthread_unwind |
| 1622 | |
| 1623 | 86641 memcheck doesn't work with Mesa OpenGL/ATI on Suse 9.1 |
| 1624 | (also fixes 74298, a duplicate of this) |
| 1625 | |
| 1626 | 85947 MMX/SSE unhandled instruction 'sfence' |
| 1627 | |
| 1628 | 84978 Wrong error "Conditional jump or move depends on |
| 1629 | uninitialised value" resulting from "sbbl %reg, %reg" |
| 1630 | |
| 1631 | 86254 ssort() fails when signed int return type from comparison is |
| 1632 | too small to handle result of unsigned int subtraction |
| 1633 | |
| 1634 | 87089 memalign( 4, xxx) makes valgrind assert |
| 1635 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1636 | 86407 Add support for low-level parallel port driver ioctls. |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1637 | |
| 1638 | 70587 Add timestamps to Valgrind output? (wishlist) |
| 1639 | |
| 1640 | 84937 vg_libpthread.c:2505 (se_remap): Assertion `res == 0' |
| 1641 | (fixed prior to 2.1.2) |
| 1642 | |
| 1643 | 86317 cannot load libSDL-1.2.so.0 using valgrind |
| 1644 | |
| 1645 | 86989 memcpy from mac_replace_strmem.c complains about |
| 1646 | uninitialized pointers passed when length to copy is zero |
| 1647 | |
| 1648 | 85811 gnu pascal symbol causes segmentation fault; ok in 2.0.0 |
| 1649 | |
| 1650 | 79138 writing to sbrk()'d memory causes segfault |
| 1651 | |
| 1652 | 77369 sched deadlock while signal received during pthread_join |
| 1653 | and the joined thread exited |
| 1654 | |
| 1655 | 88115 In signal handler for SIGFPE, siginfo->si_addr is wrong |
| 1656 | under Valgrind |
| 1657 | |
| 1658 | 78765 Massif crashes on app exit if FP exceptions are enabled |
| 1659 | |
| 1660 | Additionally there are the following changes, which are not |
| 1661 | connected to any bug report numbers, AFAICS: |
| 1662 | |
| 1663 | * Fix scary bug causing mis-identification of SSE stores vs |
| 1664 | loads and so causing memcheck to sometimes give nonsense results |
| 1665 | on SSE code. |
| 1666 | |
| 1667 | * Add support for the POSIX message queue system calls. |
| 1668 | |
| 1669 | * Fix to allow 32-bit Valgrind to run on AMD64 boxes. Note: this does |
| 1670 | NOT allow Valgrind to work with 64-bit executables - only with 32-bit |
| 1671 | executables on an AMD64 box. |
| 1672 | |
| 1673 | * At configure time, only check whether linux/mii.h can be processed |
| 1674 | so that we don't generate ugly warnings by trying to compile it. |
| 1675 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1676 | * Add support for POSIX clocks and timers. |
| 1677 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1678 | |
| 1679 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1680 | Developer (cvs head) release 2.1.2 (18 July 2004) |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1681 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1682 | 2.1.2 contains four months worth of bug fixes and refinements. |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1683 | Although officially a developer release, we believe it to be stable |
| 1684 | enough for widespread day-to-day use. 2.1.2 is pretty good, so try it |
| 1685 | first, although there is a chance it won't work. If so then try 2.0.0 |
| 1686 | and tell us what went wrong." 2.1.2 fixes a lot of problems present |
| 1687 | in 2.0.0 and is generally a much better product. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1688 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1689 | Relative to 2.1.1, a large number of minor problems with 2.1.1 have |
| 1690 | been fixed, and so if you use 2.1.1 you should try 2.1.2. Users of |
| 1691 | the last stable release, 2.0.0, might also want to try this release. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1692 | |
| 1693 | The following bugs, and probably many more, have been fixed. These |
| 1694 | are listed at http://bugs.kde.org. Reporting a bug for valgrind in |
| 1695 | the http://bugs.kde.org is much more likely to get you a fix than |
| 1696 | mailing developers directly, so please continue to keep sending bugs |
| 1697 | there. |
| 1698 | |
| 1699 | 76869 Crashes when running any tool under Fedora Core 2 test1 |
| 1700 | This fixes the problem with returning from a signal handler |
jseward | 0400d4d | 2004-07-17 23:26:46 +0000 | [diff] [blame] | 1701 | when VDSOs are turned off in FC2. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1702 | |
jseward | 0400d4d | 2004-07-17 23:26:46 +0000 | [diff] [blame] | 1703 | 69508 java 1.4.2 client fails with erroneous "stack size too small". |
| 1704 | This fix makes more of the pthread stack attribute related |
| 1705 | functions work properly. Java still doesn't work though. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1706 | |
| 1707 | 71906 malloc alignment should be 8, not 4 |
| 1708 | All memory returned by malloc/new etc is now at least |
| 1709 | 8-byte aligned. |
| 1710 | |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1711 | 81970 vg_alloc_ThreadState: no free slots available |
| 1712 | (closed because the workaround is simple: increase |
| 1713 | VG_N_THREADS, rebuild and try again.) |
| 1714 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1715 | 78514 Conditional jump or move depends on uninitialized value(s) |
| 1716 | (a slight mishanding of FP code in memcheck) |
| 1717 | |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1718 | 77952 pThread Support (crash) (due to initialisation-ordering probs) |
| 1719 | (also 85118) |
| 1720 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1721 | 80942 Addrcheck wasn't doing overlap checking as it should. |
| 1722 | 78048 return NULL on malloc/new etc failure, instead of asserting |
| 1723 | 73655 operator new() override in user .so files often doesn't get picked up |
| 1724 | 83060 Valgrind does not handle native kernel AIO |
| 1725 | 69872 Create proper coredumps after fatal signals |
| 1726 | 82026 failure with new glibc versions: __libc_* functions are not exported |
| 1727 | 70344 UNIMPLEMENTED FUNCTION: tcdrain |
| 1728 | 81297 Cancellation of pthread_cond_wait does not require mutex |
| 1729 | 82872 Using debug info from additional packages (wishlist) |
| 1730 | 83025 Support for ioctls FIGETBSZ and FIBMAP |
| 1731 | 83340 Support for ioctl HDIO_GET_IDENTITY |
| 1732 | 79714 Support for the semtimedop system call. |
| 1733 | 77022 Support for ioctls FBIOGET_VSCREENINFO and FBIOGET_FSCREENINFO |
| 1734 | 82098 hp2ps ansification (wishlist) |
| 1735 | 83573 Valgrind SIGSEGV on execve |
| 1736 | 82999 show which cmdline option was erroneous (wishlist) |
| 1737 | 83040 make valgrind VPATH and distcheck-clean (wishlist) |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1738 | 83998 Assertion `newfd > vgPlain_max_fd' failed (see below) |
| 1739 | 82722 Unchecked mmap in as_pad leads to mysterious failures later |
| 1740 | 78958 memcheck seg faults while running Mozilla |
jseward | a2c0800 | 2004-07-18 09:24:57 +0000 | [diff] [blame] | 1741 | 85416 Arguments with colon (e.g. --logsocket) ignored |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1742 | |
| 1743 | |
| 1744 | Additionally there are the following changes, which are not |
| 1745 | connected to any bug report numbers, AFAICS: |
| 1746 | |
| 1747 | * Rearranged address space layout relative to 2.1.1, so that |
| 1748 | Valgrind/tools will run out of memory later than currently in many |
| 1749 | circumstances. This is good news esp. for Calltree. It should |
| 1750 | be possible for client programs to allocate over 800MB of |
| 1751 | memory when using memcheck now. |
| 1752 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1753 | * Improved checking when laying out memory. Should hopefully avoid |
| 1754 | the random segmentation faults that 2.1.1 sometimes caused. |
| 1755 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1756 | * Support for Fedora Core 2 and SuSE 9.1. Improvements to NPTL |
| 1757 | support to the extent that V now works properly on NPTL-only setups. |
| 1758 | |
| 1759 | * Renamed the following options: |
| 1760 | --logfile-fd --> --log-fd |
| 1761 | --logfile --> --log-file |
| 1762 | --logsocket --> --log-socket |
| 1763 | to be consistent with each other and other options (esp. --input-fd). |
| 1764 | |
| 1765 | * Add support for SIOCGMIIPHY, SIOCGMIIREG and SIOCSMIIREG ioctls and |
| 1766 | improve the checking of other interface related ioctls. |
| 1767 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1768 | * Fix building with gcc-3.4.1. |
| 1769 | |
| 1770 | * Remove limit on number of semaphores supported. |
| 1771 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1772 | * Add support for syscalls: set_tid_address (258), acct (51). |
| 1773 | |
| 1774 | * Support instruction "repne movs" -- not official but seems to occur. |
| 1775 | |
| 1776 | * Implement an emulated soft limit for file descriptors in addition to |
| 1777 | the current reserved area, which effectively acts as a hard limit. The |
| 1778 | setrlimit system call now simply updates the emulated limits as best |
| 1779 | as possible - the hard limit is not allowed to move at all and just |
| 1780 | returns EPERM if you try and change it. This should stop reductions |
| 1781 | in the soft limit causing assertions when valgrind tries to allocate |
| 1782 | descriptors from the reserved area. |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1783 | (This actually came from bug #83998). |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1784 | |
nethercote | 76e8fd9 | 2004-07-21 10:37:31 +0000 | [diff] [blame] | 1785 | * Major overhaul of Cachegrind implementation. First user-visible change |
nethercote | 5e63bfb | 2004-07-17 12:49:53 +0000 | [diff] [blame] | 1786 | is that cachegrind.out files are now typically 90% smaller than they |
nethercote | 76e8fd9 | 2004-07-21 10:37:31 +0000 | [diff] [blame] | 1787 | used to be; code annotation times are correspondingly much smaller. |
| 1788 | Second user-visible change is that hit/miss counts for code that is |
| 1789 | unloaded at run-time is no longer dumped into a single "discard" pile, |
| 1790 | but accurately preserved. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1791 | |
| 1792 | * Client requests for telling valgrind about memory pools. |
| 1793 | |
| 1794 | |
| 1795 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1796 | Developer (cvs head) release 2.1.1 (12 March 2004) |
| 1797 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1798 | 2.1.1 contains some internal structural changes needed for V's |
jseward | e3e7704 | 2004-03-12 21:07:05 +0000 | [diff] [blame] | 1799 | long-term future. These don't affect end-users. Most notable |
| 1800 | user-visible changes are: |
| 1801 | |
| 1802 | * Greater isolation between Valgrind and the program being run, so |
| 1803 | the program is less likely to inadvertently kill Valgrind by |
| 1804 | doing wild writes. |
| 1805 | |
| 1806 | * Massif: a new space profiling tool. Try it! It's cool, and it'll |
| 1807 | tell you in detail where and when your C/C++ code is allocating heap. |
| 1808 | Draws pretty .ps pictures of memory use against time. A potentially |
| 1809 | powerful tool for making sense of your program's space use. |
| 1810 | |
| 1811 | * Fixes for many bugs, including support for more SSE2/SSE3 instructions, |
| 1812 | various signal/syscall things, and various problems with debug |
| 1813 | info readers. |
| 1814 | |
| 1815 | * Support for glibc-2.3.3 based systems. |
| 1816 | |
| 1817 | We are now doing automatic overnight build-and-test runs on a variety |
| 1818 | of distros. As a result, we believe 2.1.1 builds and runs on: |
| 1819 | Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE 9. |
| 1820 | |
| 1821 | |
| 1822 | The following bugs, and probably many more, have been fixed. These |
| 1823 | are listed at http://bugs.kde.org. Reporting a bug for valgrind in |
| 1824 | the http://bugs.kde.org is much more likely to get you a fix than |
| 1825 | mailing developers directly, so please continue to keep sending bugs |
| 1826 | there. |
| 1827 | |
| 1828 | 69616 glibc 2.3.2 w/NPTL is massively different than what valgrind expects |
| 1829 | 69856 I don't know how to instrument MMXish stuff (Helgrind) |
| 1830 | 73892 valgrind segfaults starting with Objective-C debug info |
| 1831 | (fix for S-type stabs) |
| 1832 | 73145 Valgrind complains too much about close(<reserved fd>) |
| 1833 | 73902 Shadow memory allocation seems to fail on RedHat 8.0 |
| 1834 | 68633 VG_N_SEMAPHORES too low (V itself was leaking semaphores) |
| 1835 | 75099 impossible to trace multiprocess programs |
| 1836 | 76839 the `impossible' happened: disInstr: INT but not 0x80 ! |
| 1837 | 76762 vg_to_ucode.c:3748 (dis_push_segreg): Assertion `sz == 4' failed. |
| 1838 | 76747 cannot include valgrind.h in c++ program |
| 1839 | 76223 parsing B(3,10) gave NULL type => impossible happens |
| 1840 | 75604 shmdt handling problem |
| 1841 | 76416 Problems with gcc 3.4 snap 20040225 |
| 1842 | 75614 using -gstabs when building your programs the `impossible' happened |
| 1843 | 75787 Patch for some CDROM ioctls CDORM_GET_MCN, CDROM_SEND_PACKET, |
| 1844 | 75294 gcc 3.4 snapshot's libstdc++ have unsupported instructions. |
| 1845 | (REP RET) |
| 1846 | 73326 vg_symtab2.c:272 (addScopeRange): Assertion `range->size > 0' failed. |
| 1847 | 72596 not recognizing __libc_malloc |
| 1848 | 69489 Would like to attach ddd to running program |
| 1849 | 72781 Cachegrind crashes with kde programs |
| 1850 | 73055 Illegal operand at DXTCV11CompressBlockSSE2 (more SSE opcodes) |
| 1851 | 73026 Descriptor leak check reports port numbers wrongly |
| 1852 | 71705 README_MISSING_SYSCALL_OR_IOCTL out of date |
| 1853 | 72643 Improve support for SSE/SSE2 instructions |
| 1854 | 72484 valgrind leaves it's own signal mask in place when execing |
| 1855 | 72650 Signal Handling always seems to restart system calls |
| 1856 | 72006 The mmap system call turns all errors in ENOMEM |
| 1857 | 71781 gdb attach is pretty useless |
| 1858 | 71180 unhandled instruction bytes: 0xF 0xAE 0x85 0xE8 |
| 1859 | 69886 writes to zero page cause valgrind to assert on exit |
| 1860 | 71791 crash when valgrinding gimp 1.3 (stabs reader problem) |
| 1861 | 69783 unhandled syscall: 218 |
| 1862 | 69782 unhandled instruction bytes: 0x66 0xF 0x2B 0x80 |
| 1863 | 70385 valgrind fails if the soft file descriptor limit is less |
| 1864 | than about 828 |
| 1865 | 69529 "rep; nop" should do a yield |
| 1866 | 70827 programs with lots of shared libraries report "mmap failed" |
| 1867 | for some of them when reading symbols |
| 1868 | 71028 glibc's strnlen is optimised enough to confuse valgrind |
| 1869 | |
| 1870 | |
| 1871 | |
| 1872 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1873 | Unstable (cvs head) release 2.1.0 (15 December 2003) |
| 1874 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1875 | For whatever it's worth, 2.1.0 actually seems pretty darn stable to me |
| 1876 | (Julian). It looks eminently usable, and given that it fixes some |
| 1877 | significant bugs, may well be worth using on a day-to-day basis. |
| 1878 | 2.1.0 is known to build and pass regression tests on: SuSE 9, SuSE |
| 1879 | 8.2, RedHat 8. |
| 1880 | |
| 1881 | 2.1.0 most notably includes Jeremy Fitzhardinge's complete overhaul of |
| 1882 | handling of system calls and signals, and their interaction with |
| 1883 | threads. In general, the accuracy of the system call, thread and |
| 1884 | signal simulations is much improved. Specifically: |
| 1885 | |
| 1886 | - Blocking system calls behave exactly as they do when running |
| 1887 | natively (not on valgrind). That is, if a syscall blocks only the |
| 1888 | calling thread when running natively, than it behaves the same on |
| 1889 | valgrind. No more mysterious hangs because V doesn't know that some |
| 1890 | syscall or other, should block only the calling thread. |
| 1891 | |
| 1892 | - Interrupted syscalls should now give more faithful results. |
| 1893 | |
| 1894 | - Finally, signal contexts in signal handlers are supported. As a |
| 1895 | result, konqueror on SuSE 9 no longer segfaults when notified of |
| 1896 | file changes in directories it is watching. |
| 1897 | |
| 1898 | Other changes: |
| 1899 | |
| 1900 | - Robert Walsh's file descriptor leakage checks. When enabled, |
| 1901 | Valgrind will print out a list of open file descriptors on |
| 1902 | exit. Along with each file descriptor, Valgrind prints out a stack |
| 1903 | backtrace of where the file was opened and any details relating to the |
| 1904 | file descriptor such as the file name or socket details. |
| 1905 | To use, give: --track-fds=yes |
| 1906 | |
| 1907 | - Implemented a few more SSE/SSE2 instructions. |
| 1908 | |
| 1909 | - Less crud on the stack when you do 'where' inside a GDB attach. |
| 1910 | |
| 1911 | - Fixed the following bugs: |
| 1912 | 68360: Valgrind does not compile against 2.6.0-testX kernels |
| 1913 | 68525: CVS head doesn't compile on C90 compilers |
| 1914 | 68566: pkgconfig support (wishlist) |
| 1915 | 68588: Assertion `sz == 4' failed in vg_to_ucode.c (disInstr) |
| 1916 | 69140: valgrind not able to explicitly specify a path to a binary. |
| 1917 | 69432: helgrind asserts encountering a MutexErr when there are |
| 1918 | EraserErr suppressions |
| 1919 | |
jseward | 0b12daf | 2003-12-14 14:35:28 +0000 | [diff] [blame] | 1920 | - Increase the max size of the translation cache from 200k average bbs |
| 1921 | to 300k average bbs. Programs on the size of OOo (680m17) are |
| 1922 | thrashing the cache at the smaller size, creating large numbers of |
| 1923 | retranslations and wasting significant time as a result. |
| 1924 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1925 | |
| 1926 | |
| 1927 | Stable release 2.0.0 (5 Nov 2003) |
| 1928 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1929 | |
| 1930 | 2.0.0 improves SSE/SSE2 support, fixes some minor bugs, and |
| 1931 | improves support for SuSE 9 and the Red Hat "Severn" beta. |
| 1932 | |
| 1933 | - Further improvements to SSE/SSE2 support. The entire test suite of |
| 1934 | the GNU Scientific Library (gsl-1.4) compiled with Intel Icc 7.1 |
| 1935 | 20030307Z '-g -O -xW' now works. I think this gives pretty good |
| 1936 | coverage of SSE/SSE2 floating point instructions, or at least the |
| 1937 | subset emitted by Icc. |
| 1938 | |
| 1939 | - Also added support for the following instructions: |
| 1940 | MOVNTDQ UCOMISD UNPCKLPS UNPCKHPS SQRTSS |
| 1941 | PUSH/POP %{FS,GS}, and PUSH %CS (Nb: there is no POP %CS). |
| 1942 | |
| 1943 | - CFI support for GDB version 6. Needed to enable newer GDBs |
| 1944 | to figure out where they are when using --gdb-attach=yes. |
| 1945 | |
| 1946 | - Fix this: |
| 1947 | mc_translate.c:1091 (memcheck_instrument): Assertion |
| 1948 | `u_in->size == 4 || u_in->size == 16' failed. |
| 1949 | |
| 1950 | - Return an error rather than panicing when given a bad socketcall. |
| 1951 | |
| 1952 | - Fix checking of syscall rt_sigtimedwait(). |
| 1953 | |
| 1954 | - Implement __NR_clock_gettime (syscall 265). Needed on Red Hat Severn. |
| 1955 | |
| 1956 | - Fixed bug in overlap check in strncpy() -- it was assuming the src was 'n' |
| 1957 | bytes long, when it could be shorter, which could cause false |
| 1958 | positives. |
| 1959 | |
| 1960 | - Support use of select() for very large numbers of file descriptors. |
| 1961 | |
| 1962 | - Don't fail silently if the executable is statically linked, or is |
| 1963 | setuid/setgid. Print an error message instead. |
| 1964 | |
| 1965 | - Support for old DWARF-1 format line number info. |
| 1966 | |
| 1967 | |
| 1968 | |
| 1969 | Snapshot 20031012 (12 October 2003) |
| 1970 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1971 | |
| 1972 | Three months worth of bug fixes, roughly. Most significant single |
| 1973 | change is improved SSE/SSE2 support, mostly thanks to Dirk Mueller. |
| 1974 | |
| 1975 | 20031012 builds on Red Hat Fedora ("Severn") but doesn't really work |
| 1976 | (curiosly, mozilla runs OK, but a modest "ls -l" bombs). I hope to |
| 1977 | get a working version out soon. It may or may not work ok on the |
| 1978 | forthcoming SuSE 9; I hear positive noises about it but haven't been |
| 1979 | able to verify this myself (not until I get hold of a copy of 9). |
| 1980 | |
| 1981 | A detailed list of changes, in no particular order: |
| 1982 | |
| 1983 | - Describe --gen-suppressions in the FAQ. |
| 1984 | |
| 1985 | - Syscall __NR_waitpid supported. |
| 1986 | |
| 1987 | - Minor MMX bug fix. |
| 1988 | |
| 1989 | - -v prints program's argv[] at startup. |
| 1990 | |
| 1991 | - More glibc-2.3 suppressions. |
| 1992 | |
| 1993 | - Suppressions for stack underrun bug(s) in the c++ support library |
| 1994 | distributed with Intel Icc 7.0. |
| 1995 | |
| 1996 | - Fix problems reading /proc/self/maps. |
| 1997 | |
| 1998 | - Fix a couple of messages that should have been suppressed by -q, |
| 1999 | but weren't. |
| 2000 | |
| 2001 | - Make Addrcheck understand "Overlap" suppressions. |
| 2002 | |
| 2003 | - At startup, check if program is statically linked and bail out if so. |
| 2004 | |
| 2005 | - Cachegrind: Auto-detect Intel Pentium-M, also VIA Nehemiah |
| 2006 | |
| 2007 | - Memcheck/addrcheck: minor speed optimisations |
| 2008 | |
| 2009 | - Handle syscall __NR_brk more correctly than before. |
| 2010 | |
| 2011 | - Fixed incorrect allocate/free mismatch errors when using |
| 2012 | operator new(unsigned, std::nothrow_t const&) |
| 2013 | operator new[](unsigned, std::nothrow_t const&) |
| 2014 | |
| 2015 | - Support POSIX pthread spinlocks. |
| 2016 | |
| 2017 | - Fixups for clean compilation with gcc-3.3.1. |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 2018 | |
| 2019 | - Implemented more opcodes: |
| 2020 | - push %es |
| 2021 | - push %ds |
| 2022 | - pop %es |
| 2023 | - pop %ds |
| 2024 | - movntq |
| 2025 | - sfence |
| 2026 | - pshufw |
| 2027 | - pavgb |
| 2028 | - ucomiss |
| 2029 | - enter |
daywalker | b18d253 | 2003-09-27 20:15:01 +0000 | [diff] [blame] | 2030 | - mov imm32, %esp |
| 2031 | - all "in" and "out" opcodes |
daywalker | 79aad84 | 2003-09-30 22:58:12 +0000 | [diff] [blame] | 2032 | - inc/dec %esp |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 2033 | - A whole bunch of SSE/SSE2 instructions |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 2034 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 2035 | - Memcheck: don't bomb on SSE/SSE2 code. |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 2036 | |
sewardj | 9023879 | 2003-05-05 00:23:42 +0000 | [diff] [blame] | 2037 | |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 2038 | Snapshot 20030725 (25 July 2003) |
| 2039 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2040 | |
| 2041 | Fixes some minor problems in 20030716. |
| 2042 | |
| 2043 | - Fix bugs in overlap checking for strcpy/memcpy etc. |
| 2044 | |
| 2045 | - Do overlap checking with Addrcheck as well as Memcheck. |
| 2046 | |
| 2047 | - Fix this: |
| 2048 | Memcheck: the `impossible' happened: |
| 2049 | get_error_name: unexpected type |
| 2050 | |
| 2051 | - Install headers needed to compile new skins. |
| 2052 | |
sewardj | e3dd2e0 | 2003-07-27 08:04:48 +0000 | [diff] [blame] | 2053 | - Remove leading spaces and colon in the LD_LIBRARY_PATH / LD_PRELOAD |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 2054 | passed to non-traced children. |
| 2055 | |
sewardj | b9eda95 | 2003-07-26 21:39:05 +0000 | [diff] [blame] | 2056 | - Fix file descriptor leak in valgrind-listener. |
| 2057 | |
sewardj | e3dd2e0 | 2003-07-27 08:04:48 +0000 | [diff] [blame] | 2058 | - Fix longstanding bug in which the allocation point of a |
| 2059 | block resized by realloc was not correctly set. This may |
| 2060 | have caused confusing error messages. |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 2061 | |
| 2062 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 2063 | Snapshot 20030716 (16 July 2003) |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2064 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2065 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 2066 | 20030716 is a snapshot of our current CVS head (development) branch. |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2067 | This is the branch which will become valgrind-2.0. It contains |
| 2068 | significant enhancements over the 1.9.X branch. |
| 2069 | |
| 2070 | Despite this being a snapshot of the CVS head, it is believed to be |
| 2071 | quite stable -- at least as stable as 1.9.6 or 1.0.4, if not more so |
| 2072 | -- and therefore suitable for widespread use. Please let us know asap |
| 2073 | if it causes problems for you. |
| 2074 | |
| 2075 | Two reasons for releasing a snapshot now are: |
| 2076 | |
| 2077 | - It's been a while since 1.9.6, and this snapshot fixes |
| 2078 | various problems that 1.9.6 has with threaded programs |
| 2079 | on glibc-2.3.X based systems. |
| 2080 | |
| 2081 | - So as to make available improvements in the 2.0 line. |
| 2082 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 2083 | Major changes in 20030716, as compared to 1.9.6: |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2084 | |
| 2085 | - More fixes to threading support on glibc-2.3.1 and 2.3.2-based |
| 2086 | systems (SuSE 8.2, Red Hat 9). If you have had problems |
| 2087 | with inconsistent/illogical behaviour of errno, h_errno or the DNS |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 2088 | resolver functions in threaded programs, 20030716 should improve |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2089 | matters. This snapshot seems stable enough to run OpenOffice.org |
| 2090 | 1.1rc on Red Hat 7.3, SuSE 8.2 and Red Hat 9, and that's a big |
| 2091 | threaded app if ever I saw one. |
| 2092 | |
| 2093 | - Automatic generation of suppression records; you no longer |
| 2094 | need to write them by hand. Use --gen-suppressions=yes. |
| 2095 | |
sewardj | 2151180 | 2003-07-22 17:47:42 +0000 | [diff] [blame] | 2096 | - strcpy/memcpy/etc check their arguments for overlaps, when |
| 2097 | running with the Memcheck or Addrcheck skins. |
| 2098 | |
| 2099 | - malloc_usable_size() is now supported. |
| 2100 | |
| 2101 | - new client requests: |
| 2102 | - VALGRIND_COUNT_ERRORS, VALGRIND_COUNT_LEAKS: |
| 2103 | useful with regression testing |
| 2104 | - VALGRIND_NON_SIMD_CALL[0123]: for running arbitrary functions |
| 2105 | on real CPU (use with caution!) |
| 2106 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2107 | - The GDB attach mechanism is more flexible. Allow the GDB to |
| 2108 | be run to be specified by --gdb-path=/path/to/gdb, and specify |
| 2109 | which file descriptor V will read its input from with |
| 2110 | --input-fd=<number>. |
| 2111 | |
sewardj | 2151180 | 2003-07-22 17:47:42 +0000 | [diff] [blame] | 2112 | - Cachegrind gives more accurate results (wasn't tracking instructions in |
| 2113 | malloc() and friends previously, is now). |
| 2114 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2115 | - Complete support for the MMX instruction set. |
| 2116 | |
| 2117 | - Partial support for the SSE and SSE2 instruction sets. Work for this |
| 2118 | is ongoing. About half the SSE/SSE2 instructions are done, so |
| 2119 | some SSE based programs may work. Currently you need to specify |
| 2120 | --skin=addrcheck. Basically not suitable for real use yet. |
| 2121 | |
| 2122 | - Significant speedups (10%-20%) for standard memory checking. |
| 2123 | |
| 2124 | - Fix assertion failure in pthread_once(). |
| 2125 | |
| 2126 | - Fix this: |
| 2127 | valgrind: vg_intercept.c:598 (vgAllRoadsLeadToRome_select): |
| 2128 | Assertion `ms_end >= ms_now' failed. |
| 2129 | |
| 2130 | - Implement pthread_mutexattr_setpshared. |
| 2131 | |
| 2132 | - Understand Pentium 4 branch hints. Also implemented a couple more |
| 2133 | obscure x86 instructions. |
| 2134 | |
| 2135 | - Lots of other minor bug fixes. |
| 2136 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 2137 | - We have a decent regression test system, for the first time. |
| 2138 | This doesn't help you directly, but it does make it a lot easier |
| 2139 | for us to track the quality of the system, especially across |
| 2140 | multiple linux distributions. |
| 2141 | |
| 2142 | You can run the regression tests with 'make regtest' after 'make |
| 2143 | install' completes. On SuSE 8.2 and Red Hat 9 I get this: |
| 2144 | |
| 2145 | == 84 tests, 0 stderr failures, 0 stdout failures == |
| 2146 | |
| 2147 | On Red Hat 8, I get this: |
| 2148 | |
| 2149 | == 84 tests, 2 stderr failures, 1 stdout failure == |
| 2150 | corecheck/tests/res_search (stdout) |
| 2151 | memcheck/tests/sigaltstack (stderr) |
| 2152 | |
| 2153 | sigaltstack is probably harmless. res_search doesn't work |
| 2154 | on R H 8 even running natively, so I'm not too worried. |
| 2155 | |
| 2156 | On Red Hat 7.3, a glibc-2.2.5 system, I get these harmless failures: |
| 2157 | |
| 2158 | == 84 tests, 2 stderr failures, 1 stdout failure == |
| 2159 | corecheck/tests/pth_atfork1 (stdout) |
| 2160 | corecheck/tests/pth_atfork1 (stderr) |
| 2161 | memcheck/tests/sigaltstack (stderr) |
| 2162 | |
| 2163 | You need to run on a PII system, at least, since some tests |
| 2164 | contain P6-specific instructions, and the test machine needs |
| 2165 | access to the internet so that corecheck/tests/res_search |
| 2166 | (a test that the DNS resolver works) can function. |
| 2167 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 2168 | As ever, thanks for the vast amount of feedback :) and bug reports :( |
| 2169 | We may not answer all messages, but we do at least look at all of |
| 2170 | them, and tend to fix the most frequently reported bugs. |
| 2171 | |
| 2172 | |
| 2173 | |
sewardj | 3791882 | 2003-05-05 01:05:09 +0000 | [diff] [blame] | 2174 | Version 1.9.6 (7 May 2003 or thereabouts) |
| 2175 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2176 | |
| 2177 | Major changes in 1.9.6: |
| 2178 | |
| 2179 | - Improved threading support for glibc >= 2.3.2 (SuSE 8.2, |
| 2180 | RedHat 9, to name but two ...) It turned out that 1.9.5 |
| 2181 | had problems with threading support on glibc >= 2.3.2, |
| 2182 | usually manifested by threaded programs deadlocking in system calls, |
| 2183 | or running unbelievably slowly. Hopefully these are fixed now. 1.9.6 |
| 2184 | is the first valgrind which gives reasonable support for |
| 2185 | glibc-2.3.2. Also fixed a 2.3.2 problem with pthread_atfork(). |
| 2186 | |
| 2187 | - Majorly expanded FAQ.txt. We've added workarounds for all |
| 2188 | common problems for which a workaround is known. |
| 2189 | |
| 2190 | Minor changes in 1.9.6: |
| 2191 | |
| 2192 | - Fix identification of the main thread's stack. Incorrect |
| 2193 | identification of it was causing some on-stack addresses to not get |
| 2194 | identified as such. This only affected the usefulness of some error |
| 2195 | messages; the correctness of the checks made is unchanged. |
| 2196 | |
| 2197 | - Support for kernels >= 2.5.68. |
| 2198 | |
| 2199 | - Dummy implementations of __libc_current_sigrtmin, |
| 2200 | __libc_current_sigrtmax and __libc_allocate_rtsig, hopefully |
| 2201 | good enough to keep alive programs which previously died for lack of |
| 2202 | them. |
| 2203 | |
| 2204 | - Fix bug in the VALGRIND_DISCARD_TRANSLATIONS client request. |
| 2205 | |
sewardj | 3d47b79 | 2003-05-05 22:15:35 +0000 | [diff] [blame] | 2206 | - Fix bug in the DWARF2 debug line info loader, when instructions |
| 2207 | following each other have source lines far from each other |
| 2208 | (e.g. with inlined functions). |
| 2209 | |
sewardj | 3791882 | 2003-05-05 01:05:09 +0000 | [diff] [blame] | 2210 | - Debug info reading: read symbols from both "symtab" and "dynsym" |
| 2211 | sections, rather than merely from the one that comes last in the |
| 2212 | file. |
| 2213 | |
| 2214 | - New syscall support: prctl(), creat(), lookup_dcookie(). |
| 2215 | |
| 2216 | - When checking calls to accept(), recvfrom(), getsocketopt(), |
| 2217 | don't complain if buffer values are NULL. |
| 2218 | |
| 2219 | - Try and avoid assertion failures in |
| 2220 | mash_LD_PRELOAD_and_LD_LIBRARY_PATH. |
| 2221 | |
| 2222 | - Minor bug fixes in cg_annotate. |
| 2223 | |
| 2224 | |
| 2225 | |
sewardj | 9023879 | 2003-05-05 00:23:42 +0000 | [diff] [blame] | 2226 | Version 1.9.5 (7 April 2003) |
| 2227 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2228 | |
| 2229 | It occurs to me that it would be helpful for valgrind users to record |
| 2230 | in the source distribution the changes in each release. So I now |
| 2231 | attempt to mend my errant ways :-) Changes in this and future releases |
| 2232 | will be documented in the NEWS file in the source distribution. |
| 2233 | |
| 2234 | Major changes in 1.9.5: |
| 2235 | |
| 2236 | - (Critical bug fix): Fix a bug in the FPU simulation. This was |
| 2237 | causing some floating point conditional tests not to work right. |
| 2238 | Several people reported this. If you had floating point code which |
| 2239 | didn't work right on 1.9.1 to 1.9.4, it's worth trying 1.9.5. |
| 2240 | |
| 2241 | - Partial support for Red Hat 9. RH9 uses the new Native Posix |
| 2242 | Threads Library (NPTL), instead of the older LinuxThreads. |
| 2243 | This potentially causes problems with V which will take some |
| 2244 | time to correct. In the meantime we have partially worked around |
| 2245 | this, and so 1.9.5 works on RH9. Threaded programs still work, |
| 2246 | but they may deadlock, because some system calls (accept, read, |
| 2247 | write, etc) which should be nonblocking, in fact do block. This |
| 2248 | is a known bug which we are looking into. |
| 2249 | |
| 2250 | If you can, your best bet (unfortunately) is to avoid using |
| 2251 | 1.9.5 on a Red Hat 9 system, or on any NPTL-based distribution. |
| 2252 | If your glibc is 2.3.1 or earlier, you're almost certainly OK. |
| 2253 | |
| 2254 | Minor changes in 1.9.5: |
| 2255 | |
| 2256 | - Added some #errors to valgrind.h to ensure people don't include |
| 2257 | it accidentally in their sources. This is a change from 1.0.X |
| 2258 | which was never properly documented. The right thing to include |
| 2259 | is now memcheck.h. Some people reported problems and strange |
| 2260 | behaviour when (incorrectly) including valgrind.h in code with |
| 2261 | 1.9.1 -- 1.9.4. This is no longer possible. |
| 2262 | |
| 2263 | - Add some __extension__ bits and pieces so that gcc configured |
| 2264 | for valgrind-checking compiles even with -Werror. If you |
| 2265 | don't understand this, ignore it. Of interest to gcc developers |
| 2266 | only. |
| 2267 | |
| 2268 | - Removed a pointless check which caused problems interworking |
| 2269 | with Clearcase. V would complain about shared objects whose |
| 2270 | names did not end ".so", and refuse to run. This is now fixed. |
| 2271 | In fact it was fixed in 1.9.4 but not documented. |
| 2272 | |
| 2273 | - Fixed a bug causing an assertion failure of "waiters == 1" |
| 2274 | somewhere in vg_scheduler.c, when running large threaded apps, |
| 2275 | notably MySQL. |
| 2276 | |
| 2277 | - Add support for the munlock system call (124). |
| 2278 | |
| 2279 | Some comments about future releases: |
| 2280 | |
| 2281 | 1.9.5 is, we hope, the most stable Valgrind so far. It pretty much |
| 2282 | supersedes the 1.0.X branch. If you are a valgrind packager, please |
| 2283 | consider making 1.9.5 available to your users. You can regard the |
| 2284 | 1.0.X branch as obsolete: 1.9.5 is stable and vastly superior. There |
| 2285 | are no plans at all for further releases of the 1.0.X branch. |
| 2286 | |
| 2287 | If you want a leading-edge valgrind, consider building the cvs head |
| 2288 | (from SourceForge), or getting a snapshot of it. Current cool stuff |
| 2289 | going in includes MMX support (done); SSE/SSE2 support (in progress), |
| 2290 | a significant (10-20%) performance improvement (done), and the usual |
| 2291 | large collection of minor changes. Hopefully we will be able to |
| 2292 | improve our NPTL support, but no promises. |
| 2293 | |