sewardj | 827748a | 2006-12-16 04:58:59 +0000 | [diff] [blame] | 1 | Release 3.3.0 (XX XXX 2007) |
njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 2 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | 827748a | 2006-12-16 04:58:59 +0000 | [diff] [blame] | 3 | 3.3.0 is a feature release with ... |
njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 4 | |
njn | 718d3b1 | 2006-12-16 00:54:12 +0000 | [diff] [blame] | 5 | Other user-visible changes: |
| 6 | |
| 7 | - A new suppression kind has been introduced: "Jump". This is for |
| 8 | suppressing jump-to-invalid-address errors. Previously you had to use an |
| 9 | "Addr1" suppression, which didn't make much sense. |
| 10 | |
| 11 | - The behaviour of Memcheck's client requests VALGRIND_GET_VBITS and |
| 12 | VALGRIND_SET_VBITS have changed slightly. They no longer issue |
| 13 | addressability errors -- if either array is partially unaddressable, |
| 14 | they just return 3 (as before). Also, SET_VBITS doesn't report |
| 15 | definedness errors if any of the V bits are undefined. |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 16 | |
njn | d5f4bef | 2006-12-24 07:54:19 +0000 | [diff] [blame] | 17 | Developer-visible changes: |
| 18 | |
| 19 | - The names of some functions and types within the Vex IR have changed. |
| 20 | So any existing tools will have to be updated to reflect these |
| 21 | changes. The new names should be clearer. The file |
| 22 | VEX/pub/libvex_ir.h is also much better commented, and serves as the |
| 23 | best documentation about Vex. |
| 24 | |
| 25 | |
njn | a7e4880 | 2007-01-23 05:58:52 +0000 | [diff] [blame^] | 26 | Release 3.2.2 (22 Jan 2007) |
| 27 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 28 | 3.2.2 fixes a bunch of bugs in 3.2.1, adds support for glibc-2.5 based |
| 29 | systems (openSUSE 10.2, Fedora Core 6), improves support for icc-9.X |
| 30 | compiled code, and brings modest performance improvements in some |
| 31 | areas, including amd64 floating point, powerpc support, and startup |
| 32 | responsiveness on all targets. |
| 33 | |
| 34 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 35 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 36 | bugzilla entry. We encourage you to file bugs in bugzilla |
| 37 | (http://bugs.kde.org/enter_valgrind_bug.cgi) rather than mailing the |
| 38 | developers (or mailing lists) directly. |
| 39 | |
| 40 | 129390 ppc?->IR: some kind of VMX prefetch (dstt) |
| 41 | 129968 amd64->IR: 0xF 0xAE 0x0 (fxsave) |
| 42 | 134319 ==129968 |
| 43 | 133054 'make install' fails with syntax errors |
| 44 | 118903 ==133054 |
| 45 | 132998 startup fails in when running on UML |
| 46 | 134207 pkg-config output contains @VG_PLATFORM@ |
| 47 | 134727 valgrind exits with "Value too large for defined data type" |
| 48 | n-i-bz ppc32/64: support mcrfs |
| 49 | n-i-bz Cachegrind/Callgrind: Update cache parameter detection |
| 50 | 135012 x86->IR: 0xD7 0x8A 0xE0 0xD0 (xlat) |
| 51 | 125959 ==135012 |
| 52 | 126147 x86->IR: 0xF2 0xA5 0xF 0x77 (repne movsw) |
| 53 | 136650 amd64->IR: 0xC2 0x8 0x0 |
| 54 | 135421 x86->IR: unhandled Grp5(R) case 6 |
| 55 | n-i-bz Improved documentation of the IR intermediate representation |
| 56 | n-i-bz jcxz (x86) (users list, 8 Nov) |
| 57 | n-i-bz ExeContext hashing fix |
| 58 | n-i-bz fix CFI reading failures ("Dwarf CFI 0:24 0:32 0:48 0:7") |
| 59 | n-i-bz fix Cachegrind/Callgrind simulation bug |
| 60 | n-i-bz libmpiwrap.c: fix handling of MPI_LONG_DOUBLE |
| 61 | n-i-bz make User errors suppressible |
| 62 | 136844 corrupted malloc line when using --gen-suppressions=yes |
| 63 | 138507 ==136844 |
| 64 | n-i-bz Speed up the JIT's register allocator |
| 65 | n-i-bz Fix confusing leak-checker flag hints |
| 66 | n-i-bz Support recent autoswamp versions |
| 67 | n-i-bz ppc32/64 dispatcher speedups |
| 68 | n-i-bz ppc64 front end rld/rlw improvements |
| 69 | n-i-bz ppc64 back end imm64 improvements |
| 70 | 136300 support 64K pages on ppc64-linux |
| 71 | 139124 == 136300 |
| 72 | n-i-bz fix ppc insn set tests for gcc >= 4.1 |
| 73 | 137493 x86->IR: recent binutils no-ops |
| 74 | 137714 x86->IR: 0x66 0xF 0xF7 0xC6 (maskmovdqu) |
| 75 | 138424 "failed in UME with error 22" (produce a better error msg) |
| 76 | 138856 ==138424 |
| 77 | 138627 Enhancement support for prctl ioctls |
| 78 | 138896 Add support for usb ioctls |
| 79 | 136059 ==138896 |
| 80 | 139050 ppc32->IR: mfspr 268/269 instructions not handled |
| 81 | n-i-bz ppc32->IR: lvxl/stvxl |
| 82 | n-i-bz glibc-2.5 support |
| 83 | n-i-bz memcheck: provide replacement for mempcpy |
| 84 | n-i-bz memcheck: replace bcmp in ld.so |
| 85 | n-i-bz Use 'ifndef' in VEX's Makefile correctly |
| 86 | n-i-bz Suppressions for MVL 4.0.1 on ppc32-linux |
| 87 | n-i-bz libmpiwrap.c: Fixes for MPICH |
| 88 | n-i-bz More robust handling of hinted client mmaps |
| 89 | 139776 Invalid read in unaligned memcpy with Intel compiler v9 |
| 90 | n-i-bz Generate valid XML even for very long fn names |
| 91 | n-i-bz Don't prompt about suppressions for unshown reachable leaks |
| 92 | 139910 amd64 rcl is not supported |
| 93 | n-i-bz DWARF CFI reader: handle DW_CFA_undefined |
| 94 | n-i-bz DWARF CFI reader: handle icc9 generated CFI info better |
| 95 | n-i-bz fix false uninit-value errs in icc9 generated FP code |
| 96 | n-i-bz reduce extraneous frames in libmpiwrap.c |
| 97 | n-i-bz support pselect6 on amd64-linux |
| 98 | |
| 99 | (3.2.2: 22 Jan 2007, vex r1729, valgrind r6545). |
| 100 | |
| 101 | |
sewardj | 172bce8 | 2006-09-16 01:00:35 +0000 | [diff] [blame] | 102 | Release 3.2.1 (16 Sept 2006) |
| 103 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 104 | 3.2.1 adds x86/amd64 support for all SSE3 instructions except monitor |
| 105 | and mwait, further reduces memcheck's false error rate on all |
| 106 | platforms, adds support for recent binutils (in OpenSUSE 10.2 and |
| 107 | Fedora Rawhide) and fixes a bunch of bugs in 3.2.0. Some of the fixed |
| 108 | bugs were causing large programs to segfault with --tool=callgrind and |
| 109 | --tool=cachegrind, so an upgrade is recommended. |
| 110 | |
| 111 | In view of the fact that any 3.3.0 release is unlikely to happen until |
| 112 | well into 1Q07, we intend to keep the 3.2.X line alive for a while |
| 113 | yet, and so we tentatively plan a 3.2.2 release sometime in December |
| 114 | 06. |
| 115 | |
| 116 | The fixed bugs are as follows. Note that "n-i-bz" stands for "not in |
| 117 | bugzilla" -- that is, a bug that was reported to us but never got a |
| 118 | bugzilla entry. |
| 119 | |
| 120 | n-i-bz Expanding brk() into last available page asserts |
| 121 | n-i-bz ppc64-linux stack RZ fast-case snafu |
| 122 | n-i-bz 'c' in --gen-supps=yes doesn't work |
| 123 | n-i-bz VG_N_SEGMENTS too low (users, 28 June) |
| 124 | n-i-bz VG_N_SEGNAMES too low (Stu Robinson) |
| 125 | 106852 x86->IR: fisttp (SSE3) |
| 126 | 117172 FUTEX_WAKE does not use uaddr2 |
| 127 | 124039 Lacks support for VKI_[GP]IO_UNIMAP* |
| 128 | 127521 amd64->IR: 0xF0 0x48 0xF 0xC7 (cmpxchg8b) |
| 129 | 128917 amd64->IR: 0x66 0xF 0xF6 0xC4 (psadbw,SSE2) |
| 130 | 129246 JJ: ppc32/ppc64 syscalls, w/ patch |
| 131 | 129358 x86->IR: fisttpl (SSE3) |
| 132 | 129866 cachegrind/callgrind causes executable to die |
| 133 | 130020 Can't stat .so/.exe error while reading symbols |
| 134 | 130388 Valgrind aborts when process calls malloc_trim() |
| 135 | 130638 PATCH: ppc32 missing system calls |
| 136 | 130785 amd64->IR: unhandled instruction "pushfq" |
| 137 | 131481: (HINT_NOP) vex x86->IR: 0xF 0x1F 0x0 0xF |
| 138 | 131298 ==131481 |
| 139 | 132146 Programs with long sequences of bswap[l,q]s |
| 140 | 132918 vex amd64->IR: 0xD9 0xF8 (fprem) |
| 141 | 132813 Assertion at priv/guest-x86/toIR.c:652 fails |
| 142 | 133051 'cfsi->len > 0 && cfsi->len < 2000000' failed |
| 143 | 132722 valgrind header files are not standard C |
| 144 | n-i-bz Livelocks entire machine (users list, Timothy Terriberry) |
| 145 | n-i-bz Alex Bennee mmap problem (9 Aug) |
| 146 | n-i-bz BartV: Don't print more lines of a stack-trace than were obtained. |
| 147 | n-i-bz ppc32 SuSE 10.1 redir |
| 148 | n-i-bz amd64 padding suppressions |
| 149 | n-i-bz amd64 insn printing fix. |
| 150 | n-i-bz ppc cmp reg,reg fix |
| 151 | n-i-bz x86/amd64 iropt e/rflag reduction rules |
| 152 | n-i-bz SuSE 10.1 (ppc32) minor fixes |
| 153 | 133678 amd64->IR: 0x48 0xF 0xC5 0xC0 (pextrw?) |
| 154 | 133694 aspacem assertion: aspacem_minAddr <= holeStart |
| 155 | n-i-bz callgrind: fix warning about malformed creator line |
| 156 | n-i-bz callgrind: fix annotate script for data produced with |
| 157 | --dump-instr=yes |
| 158 | n-i-bz callgrind: fix failed assertion when toggling |
| 159 | instrumentation mode |
| 160 | n-i-bz callgrind: fix annotate script fix warnings with |
| 161 | --collect-jumps=yes |
| 162 | n-i-bz docs path hardwired (Dennis Lubert) |
| 163 | |
| 164 | The following bugs were not fixed, due primarily to lack of developer |
| 165 | time, and also because bug reporters did not answer requests for |
| 166 | feedback in time for the release: |
| 167 | |
| 168 | 129390 ppc?->IR: some kind of VMX prefetch (dstt) |
| 169 | 129968 amd64->IR: 0xF 0xAE 0x0 (fxsave) |
| 170 | 133054 'make install' fails with syntax errors |
| 171 | n-i-bz Signal race condition (users list, 13 June, Johannes Berg) |
| 172 | n-i-bz Unrecognised instruction at address 0x70198EC2 (users list, |
| 173 | 19 July, Bennee) |
| 174 | 132998 startup fails in when running on UML |
| 175 | |
| 176 | The following bug was tentatively fixed on the mainline but the fix |
| 177 | was considered too risky to push into 3.2.X: |
| 178 | |
| 179 | 133154 crash when using client requests to register/deregister stack |
| 180 | |
| 181 | (3.2.1: 16 Sept 2006, vex r1658, valgrind r6070). |
| 182 | |
| 183 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 184 | Release 3.2.0 (7 June 2006) |
sewardj | 535a235 | 2006-04-18 02:04:52 +0000 | [diff] [blame] | 185 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 186 | 3.2.0 is a feature release with many significant improvements and the |
| 187 | usual collection of bug fixes. This release supports X86/Linux, |
| 188 | AMD64/Linux, PPC32/Linux and PPC64/Linux. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 189 | |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 190 | Performance, especially of Memcheck, is improved, Addrcheck has been |
| 191 | removed, Callgrind has been added, PPC64/Linux support has been added, |
| 192 | Lackey has been improved, and MPI support has been added. In detail: |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 193 | |
sewardj | f41db3c | 2006-05-26 16:06:10 +0000 | [diff] [blame] | 194 | - Memcheck has improved speed and reduced memory use. Run times are |
| 195 | typically reduced by 15-30%, averaging about 24% for SPEC CPU2000. |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 196 | The other tools have smaller but noticeable speed improvments. We |
| 197 | are interested to hear what improvements users get. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 198 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 199 | Memcheck uses less memory due to the introduction of a compressed |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 200 | representation for shadow memory. The space overhead has been |
| 201 | reduced by a factor of up to four, depending on program behaviour. |
| 202 | This means you should be able to run programs that use more memory |
| 203 | than before without hitting problems. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 204 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 205 | - Addrcheck has been removed. It has not worked since version 2.4.0, |
| 206 | and the speed and memory improvements to Memcheck make it redundant. |
| 207 | If you liked using Addrcheck because it didn't give undefined value |
| 208 | errors, you can use the new Memcheck option --undef-value-errors=no |
| 209 | to get the same behaviour. |
| 210 | |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 211 | - The number of undefined-value errors incorrectly reported by |
| 212 | Memcheck has been reduced (such false reports were already very |
| 213 | rare). In particular, efforts have been made to ensure Memcheck |
| 214 | works really well with gcc 4.0/4.1-generated code on X86/Linux and |
| 215 | AMD64/Linux. |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 216 | |
| 217 | - Josef Weidendorfer's popular Callgrind tool has been added. Folding |
sewardj | af92499 | 2006-05-26 13:51:37 +0000 | [diff] [blame] | 218 | it in was a logical step given its popularity and usefulness, and |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 219 | makes it easier for us to ensure it works "out of the box" on all |
| 220 | supported targets. The associated KDE KCachegrind GUI remains a |
| 221 | separate project. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 222 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 223 | - A new release of the Valkyrie GUI for Memcheck, version 1.2.0, |
| 224 | accompanies this release. Improvements over previous releases |
| 225 | include improved robustness, many refinements to the user interface, |
| 226 | and use of a standard autoconf/automake build system. You can get |
| 227 | it from http://www.valgrind.org/downloads/guis.html. |
| 228 | |
sewardj | 535a235 | 2006-04-18 02:04:52 +0000 | [diff] [blame] | 229 | - Valgrind now works on PPC64/Linux. As with the AMD64/Linux port, |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 230 | this supports programs using to 32G of address space. On 64-bit |
| 231 | capable PPC64/Linux setups, you get a dual architecture build so |
| 232 | that both 32-bit and 64-bit executables can be run. Linux on POWER5 |
| 233 | is supported, and POWER4 is also believed to work. Both 32-bit and |
| 234 | 64-bit DWARF2 is supported. This port is known to work well with |
| 235 | both gcc-compiled and xlc/xlf-compiled code. |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 236 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 237 | - Floating point accuracy has been improved for PPC32/Linux. |
| 238 | Specifically, the floating point rounding mode is observed on all FP |
| 239 | arithmetic operations, and multiply-accumulate instructions are |
| 240 | preserved by the compilation pipeline. This means you should get FP |
| 241 | results which are bit-for-bit identical to a native run. These |
| 242 | improvements are also present in the PPC64/Linux port. |
njn | b293916 | 2006-04-18 00:52:37 +0000 | [diff] [blame] | 243 | |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 244 | - Lackey, the example tool, has been improved: |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 245 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 246 | * It has a new option --detailed-counts (off by default) which |
| 247 | causes it to print out a count of loads, stores and ALU operations |
| 248 | done, and their sizes. |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 249 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 250 | * It has a new option --trace-mem (off by default) which causes it |
| 251 | to print out a trace of all memory accesses performed by a |
| 252 | program. It's a good starting point for building Valgrind tools |
| 253 | that need to track memory accesses. Read the comments at the top |
| 254 | of the file lackey/lk_main.c for details. |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 255 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 256 | * The original instrumentation (counting numbers of instructions, |
| 257 | jumps, etc) is now controlled by a new option --basic-counts. It |
| 258 | is on by default. |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 259 | |
| 260 | - MPI support: partial support for debugging distributed applications |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 261 | using the MPI library specification has been added. Valgrind is |
sewardj | 42fcf5d | 2006-04-08 13:16:36 +0000 | [diff] [blame] | 262 | aware of the memory state changes caused by a subset of the MPI |
| 263 | functions, and will carefully check data passed to the (P)MPI_ |
| 264 | interface. |
| 265 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 266 | - A new flag, --error-exitcode=, has been added. This allows changing |
| 267 | the exit code in runs where Valgrind reported errors, which is |
| 268 | useful when using Valgrind as part of an automated test suite. |
sewardj | b977908 | 2006-05-12 23:50:15 +0000 | [diff] [blame] | 269 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 270 | - Various segfaults when reading old-style "stabs" debug information |
| 271 | have been fixed. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 272 | |
sewardj | c9d09cc | 2006-05-27 03:22:04 +0000 | [diff] [blame] | 273 | - A simple performance evaluation suite has been added. See |
njn | 5359b6f | 2006-06-02 23:57:22 +0000 | [diff] [blame] | 274 | perf/README and README_DEVELOPERS for details. There are |
sewardj | c9d09cc | 2006-05-27 03:22:04 +0000 | [diff] [blame] | 275 | various bells and whistles. |
| 276 | |
sewardj | b70a613 | 2006-05-27 21:14:09 +0000 | [diff] [blame] | 277 | - New configuration flags: |
| 278 | --enable-only32bit |
| 279 | --enable-only64bit |
| 280 | By default, on 64 bit platforms (ppc64-linux, amd64-linux) the build |
| 281 | system will attempt to build a Valgrind which supports both 32-bit |
| 282 | and 64-bit executables. This may not be what you want, and you can |
| 283 | override the default behaviour using these flags. |
| 284 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 285 | Please note that Helgrind is still not working. We have made an |
| 286 | important step towards making it work again, however, with the |
| 287 | addition of function wrapping (see below). |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 288 | |
| 289 | Other user-visible changes: |
| 290 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 291 | - Valgrind now has the ability to intercept and wrap arbitrary |
| 292 | functions. This is a preliminary step towards making Helgrind work |
| 293 | again, and was required for MPI support. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 294 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 295 | - There are some changes to Memcheck's client requests. Some of them |
| 296 | have changed names: |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 297 | |
| 298 | MAKE_NOACCESS --> MAKE_MEM_NOACCESS |
| 299 | MAKE_WRITABLE --> MAKE_MEM_UNDEFINED |
| 300 | MAKE_READABLE --> MAKE_MEM_DEFINED |
| 301 | |
| 302 | CHECK_WRITABLE --> CHECK_MEM_IS_ADDRESSABLE |
| 303 | CHECK_READABLE --> CHECK_MEM_IS_DEFINED |
| 304 | CHECK_DEFINED --> CHECK_VALUE_IS_DEFINED |
| 305 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 306 | The reason for the change is that the old names are subtly |
| 307 | misleading. The old names will still work, but they are deprecated |
| 308 | and may be removed in a future release. |
njn | dbf7ca7 | 2006-03-31 11:57:59 +0000 | [diff] [blame] | 309 | |
| 310 | We also added a new client request: |
| 311 | |
| 312 | MAKE_MEM_DEFINED_IF_ADDRESSABLE(a, len) |
| 313 | |
| 314 | which is like MAKE_MEM_DEFINED but only affects a byte if the byte is |
| 315 | already addressable. |
| 316 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 317 | - The way client requests are encoded in the instruction stream has |
| 318 | changed. Unfortunately, this means 3.2.0 will not honour client |
| 319 | requests compiled into binaries using headers from earlier versions |
| 320 | of Valgrind. We will try to keep the client request encodings more |
| 321 | stable in future. |
njn | eaf0ca9 | 2006-04-09 01:23:29 +0000 | [diff] [blame] | 322 | |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 323 | BUGS FIXED: |
| 324 | |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 325 | 108258 NPTL pthread cleanup handlers not called |
| 326 | 117290 valgrind is sigKILL'd on startup |
| 327 | 117295 == 117290 |
| 328 | 118703 m_signals.c:1427 Assertion 'tst->status == VgTs_WaitSys' |
| 329 | 118466 add %reg, %reg generates incorrect validity for bit 0 |
| 330 | 123210 New: strlen from ld-linux on amd64 |
| 331 | 123244 DWARF2 CFI reader: unhandled CFI instruction 0:18 |
| 332 | 123248 syscalls in glibc-2.4: openat, fstatat, symlinkat |
| 333 | 123258 socketcall.recvmsg(msg.msg_iov[i] points to uninit |
| 334 | 123535 mremap(new_addr) requires MREMAP_FIXED in 4th arg |
| 335 | 123836 small typo in the doc |
| 336 | 124029 ppc compile failed: `vor' gcc 3.3.5 |
| 337 | 124222 Segfault: @@don't know what type ':' is |
| 338 | 124475 ppc32: crash (syscall?) timer_settime() |
| 339 | 124499 amd64->IR: 0xF 0xE 0x48 0x85 (femms) |
| 340 | 124528 FATAL: aspacem assertion failed: segment_is_sane |
| 341 | 124697 vex x86->IR: 0xF 0x70 0xC9 0x0 (pshufw) |
| 342 | 124892 vex x86->IR: 0xF3 0xAE (REPx SCASB) |
| 343 | 126216 == 124892 |
| 344 | 124808 ppc32: sys_sched_getaffinity() not handled |
| 345 | n-i-bz Very long stabs strings crash m_debuginfo |
| 346 | n-i-bz amd64->IR: 0x66 0xF 0xF5 (pmaddwd) |
| 347 | 125492 ppc32: support a bunch more syscalls |
| 348 | 121617 ppc32/64: coredumping gives assertion failure |
| 349 | 121814 Coregrind return error as exitcode patch |
| 350 | 126517 == 121814 |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 351 | 125607 amd64->IR: 0x66 0xF 0xA3 0x2 (btw etc) |
| 352 | 125651 amd64->IR: 0xF8 0x49 0xFF 0xE3 (clc?) |
| 353 | 126253 x86 movx is wrong |
| 354 | 126451 3.2 SVN doesn't work on ppc32 CPU's without FPU |
| 355 | 126217 increase # threads |
| 356 | 126243 vex x86->IR: popw mem |
| 357 | 126583 amd64->IR: 0x48 0xF 0xA4 0xC2 (shld $1,%rax,%rdx) |
sewardj | b70a613 | 2006-05-27 21:14:09 +0000 | [diff] [blame] | 358 | 126668 amd64->IR: 0x1C 0xFF (sbb $0xff,%al) |
| 359 | 126696 support for CDROMREADRAW ioctl and CDROMREADTOCENTRY fix |
| 360 | 126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624 |
| 361 | 126938 bad checking for syscalls linkat, renameat, symlinkat |
sewardj | 1ede80f | 2006-05-26 00:47:13 +0000 | [diff] [blame] | 362 | |
sewardj | 3ecf8f2 | 2006-06-06 21:41:22 +0000 | [diff] [blame] | 363 | (3.2.0RC1: 27 May 2006, vex r1626, valgrind r5947). |
| 364 | (3.2.0: 7 June 2006, vex r1628, valgrind r5957). |
njn | a3e9676 | 2006-03-27 12:23:44 +0000 | [diff] [blame] | 365 | |
| 366 | |
sewardj | 5065467 | 2006-03-16 11:33:14 +0000 | [diff] [blame] | 367 | Release 3.1.1 (15 March 2006) |
| 368 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 369 | 3.1.1 fixes a bunch of bugs reported in 3.1.0. There is no new |
| 370 | functionality. The fixed bugs are: |
| 371 | |
| 372 | (note: "n-i-bz" means "not in bugzilla" -- this bug does not have |
| 373 | a bugzilla entry). |
| 374 | |
| 375 | n-i-bz ppc32: fsub 3,3,3 in dispatcher doesn't clear NaNs |
| 376 | n-i-bz ppc32: __NR_{set,get}priority |
| 377 | 117332 x86: missing line info with icc 8.1 |
| 378 | 117366 amd64: 0xDD 0x7C fnstsw |
| 379 | 118274 == 117366 |
| 380 | 117367 amd64: 0xD9 0xF4 fxtract |
| 381 | 117369 amd64: __NR_getpriority (140) |
| 382 | 117419 ppc32: lfsu f5, -4(r11) |
| 383 | 117419 ppc32: fsqrt |
| 384 | 117936 more stabs problems (segfaults while reading debug info) |
| 385 | 119914 == 117936 |
| 386 | 120345 == 117936 |
| 387 | 118239 amd64: 0xF 0xAE 0x3F (clflush) |
| 388 | 118939 vm86old system call |
| 389 | n-i-bz memcheck/tests/mempool reads freed memory |
| 390 | n-i-bz AshleyP's custom-allocator assertion |
| 391 | n-i-bz Dirk strict-aliasing stuff |
| 392 | n-i-bz More space for debugger cmd line (Dan Thaler) |
| 393 | n-i-bz Clarified leak checker output message |
| 394 | n-i-bz AshleyP's --gen-suppressions output fix |
| 395 | n-i-bz cg_annotate's --sort option broken |
| 396 | n-i-bz OSet 64-bit fastcmp bug |
| 397 | n-i-bz VG_(getgroups) fix (Shinichi Noda) |
| 398 | n-i-bz ppc32: allocate from callee-saved FP/VMX regs |
| 399 | n-i-bz misaligned path word-size bug in mc_main.c |
| 400 | 119297 Incorrect error message for sse code |
| 401 | 120410 x86: prefetchw (0xF 0xD 0x48 0x4) |
| 402 | 120728 TIOCSERGETLSR, TIOCGICOUNT, HDIO_GET_DMA ioctls |
| 403 | 120658 Build fixes for gcc 2.96 |
| 404 | 120734 x86: Support for changing EIP in signal handler |
| 405 | n-i-bz memcheck/tests/zeropage de-looping fix |
| 406 | n-i-bz x86: fxtract doesn't work reliably |
| 407 | 121662 x86: lock xadd (0xF0 0xF 0xC0 0x2) |
| 408 | 121893 calloc does not always return zeroed memory |
| 409 | 121901 no support for syscall tkill |
| 410 | n-i-bz Suppression update for Debian unstable |
| 411 | 122067 amd64: fcmovnu (0xDB 0xD9) |
| 412 | n-i-bz ppc32: broken signal handling in cpu feature detection |
| 413 | n-i-bz ppc32: rounding mode problems (improved, partial fix only) |
| 414 | 119482 ppc32: mtfsb1 |
| 415 | n-i-bz ppc32: mtocrf/mfocrf |
| 416 | |
| 417 | (3.1.1: 15 March 2006, vex r1597, valgrind r5771). |
| 418 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 419 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 420 | Release 3.1.0 (25 November 2005) |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 421 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 422 | 3.1.0 is a feature release with a number of significant improvements: |
| 423 | AMD64 support is much improved, PPC32 support is good enough to be |
| 424 | usable, and the handling of memory management and address space is |
| 425 | much more robust. In detail: |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 426 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 427 | - AMD64 support is much improved. The 64-bit vs. 32-bit issues in |
| 428 | 3.0.X have been resolved, and it should "just work" now in all |
| 429 | cases. On AMD64 machines both 64-bit and 32-bit versions of |
| 430 | Valgrind are built. The right version will be invoked |
| 431 | automatically, even when using --trace-children and mixing execution |
| 432 | between 64-bit and 32-bit executables. Also, many more instructions |
| 433 | are supported. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 434 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 435 | - PPC32 support is now good enough to be usable. It should work with |
| 436 | all tools, but please let us know if you have problems. Three |
| 437 | classes of CPUs are supported: integer only (no FP, no Altivec), |
| 438 | which covers embedded PPC uses, integer and FP but no Altivec |
| 439 | (G3-ish), and CPUs capable of Altivec too (G4, G5). |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 440 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 441 | - Valgrind's address space management has been overhauled. As a |
| 442 | result, Valgrind should be much more robust with programs that use |
| 443 | large amounts of memory. There should be many fewer "memory |
| 444 | exhausted" messages, and debug symbols should be read correctly on |
| 445 | large (eg. 300MB+) executables. On 32-bit machines the full address |
| 446 | space available to user programs (usually 3GB or 4GB) can be fully |
| 447 | utilised. On 64-bit machines up to 32GB of space is usable; when |
| 448 | using Memcheck that means your program can use up to about 14GB. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 449 | |
| 450 | A side effect of this change is that Valgrind is no longer protected |
| 451 | against wild writes by the client. This feature was nice but relied |
| 452 | on the x86 segment registers and so wasn't portable. |
| 453 | |
| 454 | - Most users should not notice, but as part of the address space |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 455 | manager change, the way Valgrind is built has been changed. Each |
| 456 | tool is now built as a statically linked stand-alone executable, |
| 457 | rather than as a shared object that is dynamically linked with the |
| 458 | core. The "valgrind" program invokes the appropriate tool depending |
| 459 | on the --tool option. This slightly increases the amount of disk |
| 460 | space used by Valgrind, but it greatly simplified many things and |
| 461 | removed Valgrind's dependence on glibc. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 462 | |
njn | 336c89d | 2005-11-20 18:14:04 +0000 | [diff] [blame] | 463 | Please note that Addrcheck and Helgrind are still not working. Work |
| 464 | is underway to reinstate them (or equivalents). We apologise for the |
| 465 | inconvenience. |
| 466 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 467 | Other user-visible changes: |
| 468 | |
| 469 | - The --weird-hacks option has been renamed --sim-hints. |
| 470 | |
| 471 | - The --time-stamp option no longer gives an absolute date and time. |
| 472 | It now prints the time elapsed since the program began. |
| 473 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 474 | - It should build with gcc-2.96. |
| 475 | |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 476 | - Valgrind can now run itself (see README_DEVELOPERS for how). |
sewardj | 4705861 | 2005-11-16 19:13:13 +0000 | [diff] [blame] | 477 | This is not much use to you, but it means the developers can now |
| 478 | profile Valgrind using Cachegrind. As a result a couple of |
| 479 | performance bad cases have been fixed. |
| 480 | |
sewardj | 6a5a69c | 2005-11-17 00:51:36 +0000 | [diff] [blame] | 481 | - The XML output format has changed slightly. See |
| 482 | docs/internals/xml-output.txt. |
| 483 | |
njn | 14c9add | 2005-11-18 17:36:01 +0000 | [diff] [blame] | 484 | - Core dumping has been reinstated (it was disabled in 3.0.0 and 3.0.1). |
| 485 | If your program crashes while running under Valgrind, a core file with |
| 486 | the name "vgcore.<pid>" will be created (if your settings allow core |
| 487 | file creation). Note that the floating point information is not all |
| 488 | there. If Valgrind itself crashes, the OS will create a normal core |
| 489 | file. |
| 490 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 491 | The following are some user-visible changes that occurred in earlier |
| 492 | versions that may not have been announced, or were announced but not |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 493 | widely noticed. So we're mentioning them now. |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 494 | |
| 495 | - The --tool flag is optional once again; if you omit it, Memcheck |
| 496 | is run by default. |
| 497 | |
| 498 | - The --num-callers flag now has a default value of 12. It was |
| 499 | previously 4. |
| 500 | |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 501 | - The --xml=yes flag causes Valgrind's output to be produced in XML |
| 502 | format. This is designed to make it easy for other programs to |
| 503 | consume Valgrind's output. The format is described in the file |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 504 | docs/internals/xml-format.txt. |
| 505 | |
njn | 1f50399 | 2005-11-13 16:41:15 +0000 | [diff] [blame] | 506 | - The --gen-suppressions flag supports an "all" value that causes every |
| 507 | suppression to be printed without asking. |
| 508 | |
njn | ee88d28 | 2005-11-20 17:19:28 +0000 | [diff] [blame] | 509 | - The --log-file option no longer puts "pid" in the filename, eg. the |
| 510 | old name "foo.pid12345" is now "foo.12345". |
| 511 | |
njn | c66077e | 2005-11-20 18:02:15 +0000 | [diff] [blame] | 512 | - There are several graphical front-ends for Valgrind, such as Valkyrie, |
| 513 | Alleyoop and Valgui. See http://www.valgrind.org/downloads/guis.html |
| 514 | for a list. |
| 515 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 516 | BUGS FIXED: |
| 517 | |
sewardj | 4bbe9d7 | 2005-11-16 18:39:25 +0000 | [diff] [blame] | 518 | 109861 amd64 hangs at startup |
| 519 | 110301 ditto |
| 520 | 111554 valgrind crashes with Cannot allocate memory |
| 521 | 111809 Memcheck tool doesn't start java |
| 522 | 111901 cross-platform run of cachegrind fails on opteron |
| 523 | 113468 (vgPlain_mprotect_range): Assertion 'r != -1' failed. |
| 524 | 92071 Reading debugging info uses too much memory |
| 525 | 109744 memcheck loses track of mmap from direct ld-linux.so.2 |
| 526 | 110183 tail of page with _end |
| 527 | 82301 FV memory layout too rigid |
| 528 | 98278 Infinite recursion possible when allocating memory |
| 529 | 108994 Valgrind runs out of memory due to 133x overhead |
| 530 | 115643 valgrind cannot allocate memory |
| 531 | 105974 vg_hashtable.c static hash table |
| 532 | 109323 ppc32: dispatch.S uses Altivec insn, which doesn't work on POWER. |
| 533 | 109345 ptrace_setregs not yet implemented for ppc |
| 534 | 110831 Would like to be able to run against both 32 and 64 bit |
| 535 | binaries on AMD64 |
| 536 | 110829 == 110831 |
| 537 | 111781 compile of valgrind-3.0.0 fails on my linux (gcc 2.X prob) |
| 538 | 112670 Cachegrind: cg_main.c:486 (handleOneStatement ... |
| 539 | 112941 vex x86: 0xD9 0xF4 (fxtract) |
| 540 | 110201 == 112941 |
| 541 | 113015 vex amd64->IR: 0xE3 0x14 0x48 0x83 (jrcxz) |
| 542 | 113126 Crash with binaries built with -gstabs+/-ggdb |
| 543 | 104065 == 113126 |
| 544 | 115741 == 113126 |
| 545 | 113403 Partial SSE3 support on x86 |
| 546 | 113541 vex: Grp5(x86) (alt encoding inc/dec) case 1 |
| 547 | 113642 valgrind crashes when trying to read debug information |
| 548 | 113810 vex x86->IR: 66 0F F6 (66 + PSADBW == SSE PSADBW) |
| 549 | 113796 read() and write() do not work if buffer is in shared memory |
| 550 | 113851 vex x86->IR: (pmaddwd): 0x66 0xF 0xF5 0xC7 |
| 551 | 114366 vex amd64 cannnot handle __asm__( "fninit" ) |
| 552 | 114412 vex amd64->IR: 0xF 0xAD 0xC2 0xD3 (128-bit shift, shrdq?) |
| 553 | 114455 vex amd64->IR: 0xF 0xAC 0xD0 0x1 (also shrdq) |
| 554 | 115590: amd64->IR: 0x67 0xE3 0x9 0xEB (address size override) |
| 555 | 115953 valgrind svn r5042 does not build with parallel make (-j3) |
| 556 | 116057 maximum instruction size - VG_MAX_INSTR_SZB too small? |
| 557 | 116483 shmat failes with invalid argument |
| 558 | 102202 valgrind crashes when realloc'ing until out of memory |
| 559 | 109487 == 102202 |
| 560 | 110536 == 102202 |
| 561 | 112687 == 102202 |
| 562 | 111724 vex amd64->IR: 0x41 0xF 0xAB (more BT{,S,R,C} fun n games) |
| 563 | 111748 vex amd64->IR: 0xDD 0xE2 (fucom) |
| 564 | 111785 make fails if CC contains spaces |
| 565 | 111829 vex x86->IR: sbb AL, Ib |
| 566 | 111851 vex x86->IR: 0x9F 0x89 (lahf/sahf) |
| 567 | 112031 iopl on AMD64 and README_MISSING_SYSCALL_OR_IOCTL update |
| 568 | 112152 code generation for Xin_MFence on x86 with SSE0 subarch |
| 569 | 112167 == 112152 |
| 570 | 112789 == 112152 |
| 571 | 112199 naked ar tool is used in vex makefile |
| 572 | 112501 vex x86->IR: movq (0xF 0x7F 0xC1 0xF) (mmx MOVQ) |
| 573 | 113583 == 112501 |
| 574 | 112538 memalign crash |
| 575 | 113190 Broken links in docs/html/ |
| 576 | 113230 Valgrind sys_pipe on x86-64 wrongly thinks file descriptors |
| 577 | should be 64bit |
| 578 | 113996 vex amd64->IR: fucomp (0xDD 0xE9) |
| 579 | 114196 vex x86->IR: out %eax,(%dx) (0xEF 0xC9 0xC3 0x90) |
| 580 | 114289 Memcheck fails to intercept malloc when used in an uclibc environment |
| 581 | 114756 mbind syscall support |
| 582 | 114757 Valgrind dies with assertion: Assertion 'noLargerThan > 0' failed |
| 583 | 114563 stack tracking module not informed when valgrind switches threads |
| 584 | 114564 clone() and stacks |
| 585 | 114565 == 114564 |
| 586 | 115496 glibc crashes trying to use sysinfo page |
| 587 | 116200 enable fsetxattr, fgetxattr, and fremovexattr for amd64 |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 588 | |
sewardj | ae17e7e | 2005-11-20 19:45:30 +0000 | [diff] [blame] | 589 | (3.1.0RC1: 20 November 2005, vex r1466, valgrind r5224). |
sewardj | fa46202 | 2005-11-26 13:38:58 +0000 | [diff] [blame] | 590 | (3.1.0: 26 November 2005, vex r1471, valgrind r5235). |
sewardj | ae17e7e | 2005-11-20 19:45:30 +0000 | [diff] [blame] | 591 | |
njn | f63170c | 2005-11-12 19:09:51 +0000 | [diff] [blame] | 592 | |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 593 | Release 3.0.1 (29 August 2005) |
| 594 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 595 | 3.0.1 fixes a bunch of bugs reported in 3.0.0. There is no new |
| 596 | functionality. Some of the fixed bugs are critical, so if you |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 597 | 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] | 598 | bugs are: |
| 599 | |
| 600 | (note: "n-i-bz" means "not in bugzilla" -- this bug does not have |
| 601 | a bugzilla entry). |
| 602 | |
| 603 | 109313 (== 110505) x86 cmpxchg8b |
| 604 | n-i-bz x86: track but ignore changes to %eflags.AC (alignment check) |
| 605 | 110102 dis_op2_E_G(amd64) |
| 606 | 110202 x86 sys_waitpid(#286) |
| 607 | 110203 clock_getres(,0) |
| 608 | 110208 execve fail wrong retval |
| 609 | 110274 SSE1 now mandatory for x86 |
| 610 | 110388 amd64 0xDD 0xD1 |
| 611 | 110464 amd64 0xDC 0x1D FCOMP |
| 612 | 110478 amd64 0xF 0xD PREFETCH |
| 613 | n-i-bz XML <unique> printing wrong |
| 614 | n-i-bz Dirk r4359 (amd64 syscalls from trunk) |
| 615 | 110591 amd64 and x86: rdtsc not implemented properly |
| 616 | n-i-bz Nick r4384 (stub implementations of Addrcheck and Helgrind) |
| 617 | 110652 AMD64 valgrind crashes on cwtd instruction |
| 618 | 110653 AMD64 valgrind crashes on sarb $0x4,foo(%rip) instruction |
| 619 | 110656 PATH=/usr/bin::/bin valgrind foobar stats ./fooba |
| 620 | 110657 Small test fixes |
| 621 | 110671 vex x86->IR: unhandled instruction bytes: 0xF3 0xC3 (rep ret) |
| 622 | n-i-bz Nick (Cachegrind should not assert when it encounters a client |
| 623 | request.) |
| 624 | 110685 amd64->IR: unhandled instruction bytes: 0xE1 0x56 (loope Jb) |
| 625 | 110830 configuring with --host fails to build 32 bit on 64 bit target |
| 626 | 110875 Assertion when execve fails |
| 627 | n-i-bz Updates to Memcheck manual |
| 628 | n-i-bz Fixed broken malloc_usable_size() |
| 629 | 110898 opteron instructions missing: btq btsq btrq bsfq |
| 630 | 110954 x86->IR: unhandled instruction bytes: 0xE2 0xF6 (loop Jb) |
| 631 | n-i-bz Make suppressions work for "???" lines in stacktraces. |
| 632 | 111006 bogus warnings from linuxthreads |
| 633 | 111092 x86: dis_Grp2(Reg): unhandled case(x86) |
| 634 | 111231 sctp_getladdrs() and sctp_getpaddrs() returns uninitialized |
| 635 | memory |
| 636 | 111102 (comment #4) Fixed 64-bit unclean "silly arg" message |
| 637 | n-i-bz vex x86->IR: unhandled instruction bytes: 0x14 0x0 |
| 638 | n-i-bz minor umount/fcntl wrapper fixes |
| 639 | 111090 Internal Error running Massif |
| 640 | 101204 noisy warning |
| 641 | 111513 Illegal opcode for SSE instruction (x86 movups) |
| 642 | 111555 VEX/Makefile: CC is set to gcc |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 643 | n-i-bz Fix XML bugs in FAQ |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 644 | |
sewardj | fa23389 | 2005-08-30 12:35:36 +0000 | [diff] [blame] | 645 | (3.0.1: 29 August 05, |
| 646 | vex/branches/VEX_3_0_BRANCH r1367, |
| 647 | valgrind/branches/VALGRIND_3_0_BRANCH r4574). |
sewardj | 820c772 | 2005-08-29 13:44:43 +0000 | [diff] [blame] | 648 | |
| 649 | |
sewardj | cd62fe7 | 2005-08-29 13:24:51 +0000 | [diff] [blame] | 650 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 651 | Release 3.0.0 (3 August 2005) |
| 652 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 653 | 3.0.0 is a major overhaul of Valgrind. The most significant user |
| 654 | visible change is that Valgrind now supports architectures other than |
| 655 | x86. The new architectures it supports are AMD64 and PPC32, and the |
| 656 | infrastructure is present for other architectures to be added later. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 657 | |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 658 | AMD64 support works well, but has some shortcomings: |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 659 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 660 | - It generally won't be as solid as the x86 version. For example, |
| 661 | support for more obscure instructions and system calls may be missing. |
| 662 | We will fix these as they arise. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 663 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 664 | - Address space may be limited; see the point about |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 665 | position-independent executables below. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 666 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 667 | - If Valgrind is built on an AMD64 machine, it will only run 64-bit |
| 668 | executables. If you want to run 32-bit x86 executables under Valgrind |
| 669 | on an AMD64, you will need to build Valgrind on an x86 machine and |
| 670 | copy it to the AMD64 machine. And it probably won't work if you do |
| 671 | something tricky like exec'ing a 32-bit program from a 64-bit program |
| 672 | while using --trace-children=yes. We hope to improve this situation |
| 673 | in the future. |
| 674 | |
| 675 | The PPC32 support is very basic. It may not work reliably even for |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 676 | small programs, but it's a start. Many thanks to Paul Mackerras for |
| 677 | his great work that enabled this support. We are working to make |
| 678 | PPC32 usable as soon as possible. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 679 | |
| 680 | Other user-visible changes: |
| 681 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 682 | - Valgrind is no longer built by default as a position-independent |
| 683 | executable (PIE), as this caused too many problems. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 684 | |
| 685 | Without PIE enabled, AMD64 programs will only be able to access 2GB of |
| 686 | address space. We will fix this eventually, but not for the moment. |
| 687 | |
| 688 | Use --enable-pie at configure-time to turn this on. |
| 689 | |
| 690 | - Support for programs that use stack-switching has been improved. Use |
| 691 | the --max-stackframe flag for simple cases, and the |
| 692 | VALGRIND_STACK_REGISTER, VALGRIND_STACK_DEREGISTER and |
| 693 | VALGRIND_STACK_CHANGE client requests for trickier cases. |
| 694 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 695 | - Support for programs that use self-modifying code has been improved, |
| 696 | in particular programs that put temporary code fragments on the stack. |
| 697 | This helps for C programs compiled with GCC that use nested functions, |
njn | e772332 | 2005-07-24 17:19:09 +0000 | [diff] [blame] | 698 | and also Ada programs. This is controlled with the --smc-check |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 699 | flag, although the default setting should work in most cases. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 700 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 701 | - Output can now be printed in XML format. This should make it easier |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 702 | for tools such as GUI front-ends and automated error-processing |
| 703 | schemes to use Valgrind output as input. The --xml flag controls this. |
| 704 | As part of this change, ELF directory information is read from executables, |
| 705 | so absolute source file paths are available if needed. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 706 | |
| 707 | - Programs that allocate many heap blocks may run faster, due to |
| 708 | improvements in certain data structures. |
| 709 | |
njn | 7b1a6a4 | 2005-07-20 04:20:44 +0000 | [diff] [blame] | 710 | - Addrcheck is currently not working. We hope to get it working again |
| 711 | soon. Helgrind is still not working, as was the case for the 2.4.0 |
| 712 | release. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 713 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 714 | - The JITter has been completely rewritten, and is now in a separate |
| 715 | library, called Vex. This enabled a lot of the user-visible changes, |
| 716 | such as new architecture support. The new JIT unfortunately translates |
| 717 | more slowly than the old one, so programs may take longer to start. |
| 718 | We believe the code quality is produces is about the same, so once |
| 719 | started, programs should run at about the same speed. Feedback about |
| 720 | this would be useful. |
| 721 | |
| 722 | On the plus side, Vex and hence Memcheck tracks value flow properly |
| 723 | through floating point and vector registers, something the 2.X line |
| 724 | could not do. That means that Memcheck is much more likely to be |
| 725 | usably accurate on vectorised code. |
| 726 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 727 | - There is a subtle change to the way exiting of threaded programs |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 728 | is handled. In 3.0, Valgrind's final diagnostic output (leak check, |
| 729 | etc) is not printed until the last thread exits. If the last thread |
| 730 | to exit was not the original thread which started the program, any |
| 731 | other process wait()-ing on this one to exit may conclude it has |
| 732 | finished before the diagnostic output is printed. This may not be |
| 733 | what you expect. 2.X had a different scheme which avoided this |
| 734 | problem, but caused deadlocks under obscure circumstances, so we |
| 735 | are trying something different for 3.0. |
| 736 | |
| 737 | - Small changes in control log file naming which make it easier to |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 738 | use valgrind for debugging MPI-based programs. The relevant |
| 739 | new flags are --log-file-exactly= and --log-file-qualifier=. |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 740 | |
| 741 | - As part of adding AMD64 support, DWARF2 CFI-based stack unwinding |
| 742 | support was added. In principle this means Valgrind can produce |
| 743 | meaningful backtraces on x86 code compiled with -fomit-frame-pointer |
tom | 81868f0 | 2005-07-27 10:33:08 +0000 | [diff] [blame] | 744 | providing you also compile your code with -fasynchronous-unwind-tables. |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 745 | |
sewardj | ec39f33 | 2005-08-02 15:28:07 +0000 | [diff] [blame] | 746 | - The documentation build system has been completely redone. |
| 747 | The documentation masters are now in XML format, and from that |
| 748 | HTML, PostScript and PDF documentation is generated. As a result |
| 749 | the manual is now available in book form. Note that the |
| 750 | documentation in the source tarballs is pre-built, so you don't need |
| 751 | any XML processing tools to build Valgrind from a tarball. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 752 | |
| 753 | Changes that are not user-visible: |
| 754 | |
sewardj | c371bd0 | 2005-07-27 09:55:24 +0000 | [diff] [blame] | 755 | - The code has been massively overhauled in order to modularise it. |
| 756 | As a result we hope it is easier to navigate and understand. |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 757 | |
| 758 | - Lots of code has been rewritten. |
| 759 | |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 760 | BUGS FIXED: |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 761 | |
sewardj | 79bd9b6 | 2005-08-03 16:40:10 +0000 | [diff] [blame] | 762 | 110046 sz == 4 assertion failed |
| 763 | 109810 vex amd64->IR: unhandled instruction bytes: 0xA3 0x4C 0x70 0xD7 |
sewardj | f9929e6 | 2005-08-02 21:05:58 +0000 | [diff] [blame] | 764 | 109802 Add a plausible_stack_size command-line parameter ? |
| 765 | 109783 unhandled ioctl TIOCMGET (running hw detection tool discover) |
| 766 | 109780 unhandled ioctl BLKSSZGET (running fdisk -l /dev/hda) |
| 767 | 109718 vex x86->IR: unhandled instruction: ffreep |
| 768 | 109429 AMD64 unhandled syscall: 127 (sigpending) |
| 769 | 109401 false positive uninit in strchr from ld-linux.so.2 |
| 770 | 109385 "stabs" parse failure |
| 771 | 109378 amd64: unhandled instruction REP NOP |
| 772 | 109376 amd64: unhandled instruction LOOP Jb |
| 773 | 109363 AMD64 unhandled instruction bytes |
| 774 | 109362 AMD64 unhandled syscall: 24 (sched_yield) |
| 775 | 109358 fork() won't work with valgrind-3.0 SVN |
| 776 | 109332 amd64 unhandled instruction: ADC Ev, Gv |
| 777 | 109314 Bogus memcheck report on amd64 |
| 778 | 108883 Crash; vg_memory.c:905 (vgPlain_init_shadow_range): |
| 779 | Assertion `vgPlain_defined_init_shadow_page()' failed. |
| 780 | 108349 mincore syscall parameter checked incorrectly |
| 781 | 108059 build infrastructure: small update |
| 782 | 107524 epoll_ctl event parameter checked on EPOLL_CTL_DEL |
| 783 | 107123 Vex dies with unhandled instructions: 0xD9 0x31 0xF 0xAE |
| 784 | 106841 auxmap & openGL problems |
| 785 | 106713 SDL_Init causes valgrind to exit |
| 786 | 106352 setcontext and makecontext not handled correctly |
| 787 | 106293 addresses beyond initial client stack allocation |
| 788 | not checked in VALGRIND_DO_LEAK_CHECK |
| 789 | 106283 PIE client programs are loaded at address 0 |
| 790 | 105831 Assertion `vgPlain_defined_init_shadow_page()' failed. |
| 791 | 105039 long run-times probably due to memory manager |
| 792 | 104797 valgrind needs to be aware of BLKGETSIZE64 |
| 793 | 103594 unhandled instruction: FICOM |
| 794 | 103320 Valgrind 2.4.0 fails to compile with gcc 3.4.3 and -O0 |
| 795 | 103168 potentially memory leak in coregrind/ume.c |
| 796 | 102039 bad permissions for mapped region at address 0xB7C73680 |
| 797 | 101881 weird assertion problem |
| 798 | 101543 Support fadvise64 syscalls |
| 799 | 75247 x86_64/amd64 support (the biggest "bug" we have ever fixed) |
njn | 4a9f6f4 | 2005-07-19 23:46:08 +0000 | [diff] [blame] | 800 | |
sewardj | 9a91951 | 2005-08-03 17:01:51 +0000 | [diff] [blame] | 801 | (3.0RC1: 27 July 05, vex r1303, valgrind r4283). |
sewardj | 1346e13 | 2005-08-03 20:42:06 +0000 | [diff] [blame] | 802 | (3.0.0: 3 August 05, vex r1313, valgrind r4316). |
sewardj | bfa2b99 | 2005-07-27 17:49:17 +0000 | [diff] [blame] | 803 | |
| 804 | |
| 805 | |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 806 | Stable release 2.4.0 (March 2005) -- CHANGES RELATIVE TO 2.2.0 |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 807 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 808 | 2.4.0 brings many significant changes and bug fixes. The most |
| 809 | significant user-visible change is that we no longer supply our own |
| 810 | pthread implementation. Instead, Valgrind is finally capable of |
| 811 | running the native thread library, either LinuxThreads or NPTL. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 812 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 813 | This means our libpthread has gone, along with the bugs associated |
| 814 | with it. Valgrind now supports the kernel's threading syscalls, and |
| 815 | lets you use your standard system libpthread. As a result: |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 816 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 817 | * There are many fewer system dependencies and strange library-related |
| 818 | bugs. There is a small performance improvement, and a large |
| 819 | stability improvement. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 820 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 821 | * On the downside, Valgrind can no longer report misuses of the POSIX |
| 822 | PThreads API. It also means that Helgrind currently does not work. |
| 823 | We hope to fix these problems in a future release. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 824 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 825 | Note that running the native thread libraries does not mean Valgrind |
| 826 | is able to provide genuine concurrent execution on SMPs. We still |
| 827 | impose the restriction that only one thread is running at any given |
| 828 | time. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 829 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 830 | There are many other significant changes too: |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 831 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 832 | * Memcheck is (once again) the default tool. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 833 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 834 | * The default stack backtrace is now 12 call frames, rather than 4. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 835 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 836 | * Suppressions can have up to 25 call frame matches, rather than 4. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 837 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 838 | * Memcheck and Addrcheck use less memory. Under some circumstances, |
| 839 | they no longer allocate shadow memory if there are large regions of |
| 840 | memory with the same A/V states - such as an mmaped file. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 841 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 842 | * The memory-leak detector in Memcheck and Addrcheck has been |
| 843 | improved. It now reports more types of memory leak, including |
| 844 | leaked cycles. When reporting leaked memory, it can distinguish |
| 845 | between directly leaked memory (memory with no references), and |
| 846 | indirectly leaked memory (memory only referred to by other leaked |
| 847 | memory). |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 848 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 849 | * Memcheck's confusion over the effect of mprotect() has been fixed: |
| 850 | previously mprotect could erroneously mark undefined data as |
| 851 | defined. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 852 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 853 | * Signal handling is much improved and should be very close to what |
| 854 | you get when running natively. |
| 855 | |
| 856 | One result of this is that Valgrind observes changes to sigcontexts |
| 857 | passed to signal handlers. Such modifications will take effect when |
| 858 | the signal returns. You will need to run with --single-step=yes to |
| 859 | make this useful. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 860 | |
| 861 | * Valgrind is built in Position Independent Executable (PIE) format if |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 862 | your toolchain supports it. This allows it to take advantage of all |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 863 | the available address space on systems with 4Gbyte user address |
| 864 | spaces. |
| 865 | |
| 866 | * Valgrind can now run itself (requires PIE support). |
| 867 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 868 | * Syscall arguments are now checked for validity. Previously all |
| 869 | memory used by syscalls was checked, but now the actual values |
| 870 | passed are also checked. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 871 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 872 | * Syscall wrappers are more robust against bad addresses being passed |
| 873 | to syscalls: they will fail with EFAULT rather than killing Valgrind |
| 874 | with SIGSEGV. |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 875 | |
njn | 1aa5ae4 | 2005-03-26 16:04:27 +0000 | [diff] [blame] | 876 | * Because clone() is directly supported, some non-pthread uses of it |
| 877 | will work. Partial sharing (where some resources are shared, and |
| 878 | some are not) is not supported. |
| 879 | |
| 880 | * open() and readlink() on /proc/self/exe are supported. |
| 881 | |
| 882 | BUGS FIXED: |
| 883 | |
| 884 | 88520 pipe+fork+dup2 kills the main program |
| 885 | 88604 Valgrind Aborts when using $VALGRIND_OPTS and user progra... |
| 886 | 88614 valgrind: vg_libpthread.c:2323 (read): Assertion `read_pt... |
| 887 | 88703 Stabs parser fails to handle ";" |
| 888 | 88886 ioctl wrappers for TIOCMBIS and TIOCMBIC |
| 889 | 89032 valgrind pthread_cond_timedwait fails |
| 890 | 89106 the 'impossible' happened |
| 891 | 89139 Missing sched_setaffinity & sched_getaffinity |
| 892 | 89198 valgrind lacks support for SIOCSPGRP and SIOCGPGRP |
| 893 | 89263 Missing ioctl translations for scsi-generic and CD playing |
| 894 | 89440 tests/deadlock.c line endings |
| 895 | 89481 `impossible' happened: EXEC FAILED |
| 896 | 89663 valgrind 2.2.0 crash on Redhat 7.2 |
| 897 | 89792 Report pthread_mutex_lock() deadlocks instead of returnin... |
| 898 | 90111 statvfs64 gives invalid error/warning |
| 899 | 90128 crash+memory fault with stabs generated by gnat for a run... |
| 900 | 90778 VALGRIND_CHECK_DEFINED() not as documented in memcheck.h |
| 901 | 90834 cachegrind crashes at end of program without reporting re... |
| 902 | 91028 valgrind: vg_memory.c:229 (vgPlain_unmap_range): Assertio... |
| 903 | 91162 valgrind crash while debugging drivel 1.2.1 |
| 904 | 91199 Unimplemented function |
| 905 | 91325 Signal routing does not propagate the siginfo structure |
| 906 | 91599 Assertion `cv == ((void *)0)' |
| 907 | 91604 rw_lookup clears orig and sends the NULL value to rw_new |
| 908 | 91821 Small problems building valgrind with $top_builddir ne $t... |
| 909 | 91844 signal 11 (SIGSEGV) at get_tcb (libpthread.c:86) in corec... |
| 910 | 92264 UNIMPLEMENTED FUNCTION: pthread_condattr_setpshared |
| 911 | 92331 per-target flags necessitate AM_PROG_CC_C_O |
| 912 | 92420 valgrind doesn't compile with linux 2.6.8.1/9 |
| 913 | 92513 Valgrind 2.2.0 generates some warning messages |
| 914 | 92528 vg_symtab2.c:170 (addLoc): Assertion `loc->size > 0' failed. |
| 915 | 93096 unhandled ioctl 0x4B3A and 0x5601 |
| 916 | 93117 Tool and core interface versions do not match |
| 917 | 93128 Can't run valgrind --tool=memcheck because of unimplement... |
| 918 | 93174 Valgrind can crash if passed bad args to certain syscalls |
| 919 | 93309 Stack frame in new thread is badly aligned |
| 920 | 93328 Wrong types used with sys_sigprocmask() |
| 921 | 93763 /usr/include/asm/msr.h is missing |
| 922 | 93776 valgrind: vg_memory.c:508 (vgPlain_find_map_space): Asser... |
| 923 | 93810 fcntl() argument checking a bit too strict |
| 924 | 94378 Assertion `tst->sigqueue_head != tst->sigqueue_tail' failed. |
| 925 | 94429 valgrind 2.2.0 segfault with mmap64 in glibc 2.3.3 |
| 926 | 94645 Impossible happened: PINSRW mem |
| 927 | 94953 valgrind: the `impossible' happened: SIGSEGV |
| 928 | 95667 Valgrind does not work with any KDE app |
| 929 | 96243 Assertion 'res==0' failed |
| 930 | 96252 stage2 loader of valgrind fails to allocate memory |
| 931 | 96520 All programs crashing at _dl_start (in /lib/ld-2.3.3.so) ... |
| 932 | 96660 ioctl CDROMREADTOCENTRY causes bogus warnings |
| 933 | 96747 After looping in a segfault handler, the impossible happens |
| 934 | 96923 Zero sized arrays crash valgrind trace back with SIGFPE |
| 935 | 96948 valgrind stops with assertion failure regarding mmap2 |
| 936 | 96966 valgrind fails when application opens more than 16 sockets |
| 937 | 97398 valgrind: vg_libpthread.c:2667 Assertion failed |
| 938 | 97407 valgrind: vg_mylibc.c:1226 (vgPlain_safe_fd): Assertion `... |
| 939 | 97427 "Warning: invalid file descriptor -1 in syscall close()" ... |
| 940 | 97785 missing backtrace |
| 941 | 97792 build in obj dir fails - autoconf / makefile cleanup |
| 942 | 97880 pthread_mutex_lock fails from shared library (special ker... |
| 943 | 97975 program aborts without ang VG messages |
| 944 | 98129 Failed when open and close file 230000 times using stdio |
| 945 | 98175 Crashes when using valgrind-2.2.0 with a program using al... |
| 946 | 98288 Massif broken |
| 947 | 98303 UNIMPLEMENTED FUNCTION pthread_condattr_setpshared |
| 948 | 98630 failed--compilation missing warnings.pm, fails to make he... |
| 949 | 98756 Cannot valgrind signal-heavy kdrive X server |
| 950 | 98966 valgrinding the JVM fails with a sanity check assertion |
| 951 | 99035 Valgrind crashes while profiling |
| 952 | 99142 loops with message "Signal 11 being dropped from thread 0... |
| 953 | 99195 threaded apps crash on thread start (using QThread::start... |
| 954 | 99348 Assertion `vgPlain_lseek(core_fd, 0, 1) == phdrs[i].p_off... |
| 955 | 99568 False negative due to mishandling of mprotect |
| 956 | 99738 valgrind memcheck crashes on program that uses sigitimer |
| 957 | 99923 0-sized allocations are reported as leaks |
| 958 | 99949 program seg faults after exit() |
| 959 | 100036 "newSuperblock's request for 1048576 bytes failed" |
| 960 | 100116 valgrind: (pthread_cond_init): Assertion `sizeof(* cond) ... |
| 961 | 100486 memcheck reports "valgrind: the `impossible' happened: V... |
| 962 | 100833 second call to "mremap" fails with EINVAL |
| 963 | 101156 (vgPlain_find_map_space): Assertion `(addr & ((1 << 12)-1... |
| 964 | 101173 Assertion `recDepth >= 0 && recDepth < 500' failed |
| 965 | 101291 creating threads in a forked process fails |
| 966 | 101313 valgrind causes different behavior when resizing a window... |
| 967 | 101423 segfault for c++ array of floats |
| 968 | 101562 valgrind massif dies on SIGINT even with signal handler r... |
| 969 | |
njn | 8c92730 | 2005-03-12 16:45:01 +0000 | [diff] [blame] | 970 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 971 | Stable release 2.2.0 (31 August 2004) -- CHANGES RELATIVE TO 2.0.0 |
| 972 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
jseward | 7d180d9 | 2004-08-30 18:15:37 +0000 | [diff] [blame] | 973 | 2.2.0 brings nine months worth of improvements and bug fixes. We |
| 974 | believe it to be a worthy successor to 2.0.0. There are literally |
| 975 | hundreds of bug fixes and minor improvements. There are also some |
| 976 | fairly major user-visible changes: |
| 977 | |
| 978 | * A complete overhaul of handling of system calls and signals, and |
| 979 | their interaction with threads. In general, the accuracy of the |
| 980 | system call, thread and signal simulations is much improved: |
| 981 | |
| 982 | - Blocking system calls behave exactly as they do when running |
| 983 | natively (not on valgrind). That is, if a syscall blocks only the |
| 984 | calling thread when running natively, than it behaves the same on |
| 985 | valgrind. No more mysterious hangs because V doesn't know that some |
| 986 | syscall or other, should block only the calling thread. |
| 987 | |
| 988 | - Interrupted syscalls should now give more faithful results. |
| 989 | |
| 990 | - Signal contexts in signal handlers are supported. |
| 991 | |
| 992 | * Improvements to NPTL support to the extent that V now works |
| 993 | properly on NPTL-only setups. |
| 994 | |
| 995 | * Greater isolation between Valgrind and the program being run, so |
| 996 | the program is less likely to inadvertently kill Valgrind by |
| 997 | doing wild writes. |
| 998 | |
| 999 | * Massif: a new space profiling tool. Try it! It's cool, and it'll |
| 1000 | tell you in detail where and when your C/C++ code is allocating heap. |
| 1001 | Draws pretty .ps pictures of memory use against time. A potentially |
| 1002 | powerful tool for making sense of your program's space use. |
| 1003 | |
| 1004 | * File descriptor leakage checks. When enabled, Valgrind will print out |
| 1005 | a list of open file descriptors on exit. |
| 1006 | |
| 1007 | * Improved SSE2/SSE3 support. |
| 1008 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1009 | * Time-stamped output; use --time-stamp=yes |
| 1010 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1011 | |
| 1012 | |
| 1013 | Stable release 2.2.0 (31 August 2004) -- CHANGES RELATIVE TO 2.1.2 |
| 1014 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1015 | 2.2.0 is not much different from 2.1.2, released seven weeks ago. |
| 1016 | A number of bugs have been fixed, most notably #85658, which gave |
| 1017 | problems for quite a few people. There have been many internal |
| 1018 | cleanups, but those are not user visible. |
| 1019 | |
| 1020 | The following bugs have been fixed since 2.1.2: |
| 1021 | |
| 1022 | 85658 Assert in coregrind/vg_libpthread.c:2326 (open64) != |
| 1023 | (void*)0 failed |
| 1024 | This bug was reported multiple times, and so the following |
| 1025 | duplicates of it are also fixed: 87620, 85796, 85935, 86065, |
| 1026 | 86919, 86988, 87917, 88156 |
| 1027 | |
| 1028 | 80716 Semaphore mapping bug caused by unmap (sem_destroy) |
| 1029 | (Was fixed prior to 2.1.2) |
| 1030 | |
| 1031 | 86987 semctl and shmctl syscalls family is not handled properly |
| 1032 | |
| 1033 | 86696 valgrind 2.1.2 + RH AS2.1 + librt |
| 1034 | |
| 1035 | 86730 valgrind locks up at end of run with assertion failure |
| 1036 | in __pthread_unwind |
| 1037 | |
| 1038 | 86641 memcheck doesn't work with Mesa OpenGL/ATI on Suse 9.1 |
| 1039 | (also fixes 74298, a duplicate of this) |
| 1040 | |
| 1041 | 85947 MMX/SSE unhandled instruction 'sfence' |
| 1042 | |
| 1043 | 84978 Wrong error "Conditional jump or move depends on |
| 1044 | uninitialised value" resulting from "sbbl %reg, %reg" |
| 1045 | |
| 1046 | 86254 ssort() fails when signed int return type from comparison is |
| 1047 | too small to handle result of unsigned int subtraction |
| 1048 | |
| 1049 | 87089 memalign( 4, xxx) makes valgrind assert |
| 1050 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1051 | 86407 Add support for low-level parallel port driver ioctls. |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1052 | |
| 1053 | 70587 Add timestamps to Valgrind output? (wishlist) |
| 1054 | |
| 1055 | 84937 vg_libpthread.c:2505 (se_remap): Assertion `res == 0' |
| 1056 | (fixed prior to 2.1.2) |
| 1057 | |
| 1058 | 86317 cannot load libSDL-1.2.so.0 using valgrind |
| 1059 | |
| 1060 | 86989 memcpy from mac_replace_strmem.c complains about |
| 1061 | uninitialized pointers passed when length to copy is zero |
| 1062 | |
| 1063 | 85811 gnu pascal symbol causes segmentation fault; ok in 2.0.0 |
| 1064 | |
| 1065 | 79138 writing to sbrk()'d memory causes segfault |
| 1066 | |
| 1067 | 77369 sched deadlock while signal received during pthread_join |
| 1068 | and the joined thread exited |
| 1069 | |
| 1070 | 88115 In signal handler for SIGFPE, siginfo->si_addr is wrong |
| 1071 | under Valgrind |
| 1072 | |
| 1073 | 78765 Massif crashes on app exit if FP exceptions are enabled |
| 1074 | |
| 1075 | Additionally there are the following changes, which are not |
| 1076 | connected to any bug report numbers, AFAICS: |
| 1077 | |
| 1078 | * Fix scary bug causing mis-identification of SSE stores vs |
| 1079 | loads and so causing memcheck to sometimes give nonsense results |
| 1080 | on SSE code. |
| 1081 | |
| 1082 | * Add support for the POSIX message queue system calls. |
| 1083 | |
| 1084 | * Fix to allow 32-bit Valgrind to run on AMD64 boxes. Note: this does |
| 1085 | NOT allow Valgrind to work with 64-bit executables - only with 32-bit |
| 1086 | executables on an AMD64 box. |
| 1087 | |
| 1088 | * At configure time, only check whether linux/mii.h can be processed |
| 1089 | so that we don't generate ugly warnings by trying to compile it. |
| 1090 | |
jseward | 2eb002b | 2004-08-31 00:14:02 +0000 | [diff] [blame] | 1091 | * Add support for POSIX clocks and timers. |
| 1092 | |
jseward | 34ed74f | 2004-08-30 18:04:42 +0000 | [diff] [blame] | 1093 | |
| 1094 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1095 | Developer (cvs head) release 2.1.2 (18 July 2004) |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1096 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1097 | 2.1.2 contains four months worth of bug fixes and refinements. |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1098 | Although officially a developer release, we believe it to be stable |
| 1099 | enough for widespread day-to-day use. 2.1.2 is pretty good, so try it |
| 1100 | first, although there is a chance it won't work. If so then try 2.0.0 |
| 1101 | and tell us what went wrong." 2.1.2 fixes a lot of problems present |
| 1102 | in 2.0.0 and is generally a much better product. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1103 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1104 | Relative to 2.1.1, a large number of minor problems with 2.1.1 have |
| 1105 | been fixed, and so if you use 2.1.1 you should try 2.1.2. Users of |
| 1106 | 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] | 1107 | |
| 1108 | The following bugs, and probably many more, have been fixed. These |
| 1109 | are listed at http://bugs.kde.org. Reporting a bug for valgrind in |
| 1110 | the http://bugs.kde.org is much more likely to get you a fix than |
| 1111 | mailing developers directly, so please continue to keep sending bugs |
| 1112 | there. |
| 1113 | |
| 1114 | 76869 Crashes when running any tool under Fedora Core 2 test1 |
| 1115 | This fixes the problem with returning from a signal handler |
jseward | 0400d4d | 2004-07-17 23:26:46 +0000 | [diff] [blame] | 1116 | when VDSOs are turned off in FC2. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1117 | |
jseward | 0400d4d | 2004-07-17 23:26:46 +0000 | [diff] [blame] | 1118 | 69508 java 1.4.2 client fails with erroneous "stack size too small". |
| 1119 | This fix makes more of the pthread stack attribute related |
| 1120 | functions work properly. Java still doesn't work though. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1121 | |
| 1122 | 71906 malloc alignment should be 8, not 4 |
| 1123 | All memory returned by malloc/new etc is now at least |
| 1124 | 8-byte aligned. |
| 1125 | |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1126 | 81970 vg_alloc_ThreadState: no free slots available |
| 1127 | (closed because the workaround is simple: increase |
| 1128 | VG_N_THREADS, rebuild and try again.) |
| 1129 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1130 | 78514 Conditional jump or move depends on uninitialized value(s) |
| 1131 | (a slight mishanding of FP code in memcheck) |
| 1132 | |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1133 | 77952 pThread Support (crash) (due to initialisation-ordering probs) |
| 1134 | (also 85118) |
| 1135 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1136 | 80942 Addrcheck wasn't doing overlap checking as it should. |
| 1137 | 78048 return NULL on malloc/new etc failure, instead of asserting |
| 1138 | 73655 operator new() override in user .so files often doesn't get picked up |
| 1139 | 83060 Valgrind does not handle native kernel AIO |
| 1140 | 69872 Create proper coredumps after fatal signals |
| 1141 | 82026 failure with new glibc versions: __libc_* functions are not exported |
| 1142 | 70344 UNIMPLEMENTED FUNCTION: tcdrain |
| 1143 | 81297 Cancellation of pthread_cond_wait does not require mutex |
| 1144 | 82872 Using debug info from additional packages (wishlist) |
| 1145 | 83025 Support for ioctls FIGETBSZ and FIBMAP |
| 1146 | 83340 Support for ioctl HDIO_GET_IDENTITY |
| 1147 | 79714 Support for the semtimedop system call. |
| 1148 | 77022 Support for ioctls FBIOGET_VSCREENINFO and FBIOGET_FSCREENINFO |
| 1149 | 82098 hp2ps ansification (wishlist) |
| 1150 | 83573 Valgrind SIGSEGV on execve |
| 1151 | 82999 show which cmdline option was erroneous (wishlist) |
| 1152 | 83040 make valgrind VPATH and distcheck-clean (wishlist) |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1153 | 83998 Assertion `newfd > vgPlain_max_fd' failed (see below) |
| 1154 | 82722 Unchecked mmap in as_pad leads to mysterious failures later |
| 1155 | 78958 memcheck seg faults while running Mozilla |
jseward | a2c0800 | 2004-07-18 09:24:57 +0000 | [diff] [blame] | 1156 | 85416 Arguments with colon (e.g. --logsocket) ignored |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1157 | |
| 1158 | |
| 1159 | Additionally there are the following changes, which are not |
| 1160 | connected to any bug report numbers, AFAICS: |
| 1161 | |
| 1162 | * Rearranged address space layout relative to 2.1.1, so that |
| 1163 | Valgrind/tools will run out of memory later than currently in many |
| 1164 | circumstances. This is good news esp. for Calltree. It should |
| 1165 | be possible for client programs to allocate over 800MB of |
| 1166 | memory when using memcheck now. |
| 1167 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1168 | * Improved checking when laying out memory. Should hopefully avoid |
| 1169 | the random segmentation faults that 2.1.1 sometimes caused. |
| 1170 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1171 | * Support for Fedora Core 2 and SuSE 9.1. Improvements to NPTL |
| 1172 | support to the extent that V now works properly on NPTL-only setups. |
| 1173 | |
| 1174 | * Renamed the following options: |
| 1175 | --logfile-fd --> --log-fd |
| 1176 | --logfile --> --log-file |
| 1177 | --logsocket --> --log-socket |
| 1178 | to be consistent with each other and other options (esp. --input-fd). |
| 1179 | |
| 1180 | * Add support for SIOCGMIIPHY, SIOCGMIIREG and SIOCSMIIREG ioctls and |
| 1181 | improve the checking of other interface related ioctls. |
| 1182 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1183 | * Fix building with gcc-3.4.1. |
| 1184 | |
| 1185 | * Remove limit on number of semaphores supported. |
| 1186 | |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1187 | * Add support for syscalls: set_tid_address (258), acct (51). |
| 1188 | |
| 1189 | * Support instruction "repne movs" -- not official but seems to occur. |
| 1190 | |
| 1191 | * Implement an emulated soft limit for file descriptors in addition to |
| 1192 | the current reserved area, which effectively acts as a hard limit. The |
| 1193 | setrlimit system call now simply updates the emulated limits as best |
| 1194 | as possible - the hard limit is not allowed to move at all and just |
| 1195 | returns EPERM if you try and change it. This should stop reductions |
| 1196 | in the soft limit causing assertions when valgrind tries to allocate |
| 1197 | descriptors from the reserved area. |
jseward | a6017a4 | 2004-07-17 23:44:35 +0000 | [diff] [blame] | 1198 | (This actually came from bug #83998). |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1199 | |
nethercote | 76e8fd9 | 2004-07-21 10:37:31 +0000 | [diff] [blame] | 1200 | * Major overhaul of Cachegrind implementation. First user-visible change |
nethercote | 5e63bfb | 2004-07-17 12:49:53 +0000 | [diff] [blame] | 1201 | is that cachegrind.out files are now typically 90% smaller than they |
nethercote | 76e8fd9 | 2004-07-21 10:37:31 +0000 | [diff] [blame] | 1202 | used to be; code annotation times are correspondingly much smaller. |
| 1203 | Second user-visible change is that hit/miss counts for code that is |
| 1204 | unloaded at run-time is no longer dumped into a single "discard" pile, |
| 1205 | but accurately preserved. |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1206 | |
| 1207 | * Client requests for telling valgrind about memory pools. |
| 1208 | |
| 1209 | |
| 1210 | |
jseward | 9cd978c | 2004-07-17 13:38:12 +0000 | [diff] [blame] | 1211 | Developer (cvs head) release 2.1.1 (12 March 2004) |
| 1212 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
jseward | bd0a6e4 | 2004-07-17 12:19:43 +0000 | [diff] [blame] | 1213 | 2.1.1 contains some internal structural changes needed for V's |
jseward | e3e7704 | 2004-03-12 21:07:05 +0000 | [diff] [blame] | 1214 | long-term future. These don't affect end-users. Most notable |
| 1215 | user-visible changes are: |
| 1216 | |
| 1217 | * Greater isolation between Valgrind and the program being run, so |
| 1218 | the program is less likely to inadvertently kill Valgrind by |
| 1219 | doing wild writes. |
| 1220 | |
| 1221 | * Massif: a new space profiling tool. Try it! It's cool, and it'll |
| 1222 | tell you in detail where and when your C/C++ code is allocating heap. |
| 1223 | Draws pretty .ps pictures of memory use against time. A potentially |
| 1224 | powerful tool for making sense of your program's space use. |
| 1225 | |
| 1226 | * Fixes for many bugs, including support for more SSE2/SSE3 instructions, |
| 1227 | various signal/syscall things, and various problems with debug |
| 1228 | info readers. |
| 1229 | |
| 1230 | * Support for glibc-2.3.3 based systems. |
| 1231 | |
| 1232 | We are now doing automatic overnight build-and-test runs on a variety |
| 1233 | of distros. As a result, we believe 2.1.1 builds and runs on: |
| 1234 | Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE 9. |
| 1235 | |
| 1236 | |
| 1237 | The following bugs, and probably many more, have been fixed. These |
| 1238 | are listed at http://bugs.kde.org. Reporting a bug for valgrind in |
| 1239 | the http://bugs.kde.org is much more likely to get you a fix than |
| 1240 | mailing developers directly, so please continue to keep sending bugs |
| 1241 | there. |
| 1242 | |
| 1243 | 69616 glibc 2.3.2 w/NPTL is massively different than what valgrind expects |
| 1244 | 69856 I don't know how to instrument MMXish stuff (Helgrind) |
| 1245 | 73892 valgrind segfaults starting with Objective-C debug info |
| 1246 | (fix for S-type stabs) |
| 1247 | 73145 Valgrind complains too much about close(<reserved fd>) |
| 1248 | 73902 Shadow memory allocation seems to fail on RedHat 8.0 |
| 1249 | 68633 VG_N_SEMAPHORES too low (V itself was leaking semaphores) |
| 1250 | 75099 impossible to trace multiprocess programs |
| 1251 | 76839 the `impossible' happened: disInstr: INT but not 0x80 ! |
| 1252 | 76762 vg_to_ucode.c:3748 (dis_push_segreg): Assertion `sz == 4' failed. |
| 1253 | 76747 cannot include valgrind.h in c++ program |
| 1254 | 76223 parsing B(3,10) gave NULL type => impossible happens |
| 1255 | 75604 shmdt handling problem |
| 1256 | 76416 Problems with gcc 3.4 snap 20040225 |
| 1257 | 75614 using -gstabs when building your programs the `impossible' happened |
| 1258 | 75787 Patch for some CDROM ioctls CDORM_GET_MCN, CDROM_SEND_PACKET, |
| 1259 | 75294 gcc 3.4 snapshot's libstdc++ have unsupported instructions. |
| 1260 | (REP RET) |
| 1261 | 73326 vg_symtab2.c:272 (addScopeRange): Assertion `range->size > 0' failed. |
| 1262 | 72596 not recognizing __libc_malloc |
| 1263 | 69489 Would like to attach ddd to running program |
| 1264 | 72781 Cachegrind crashes with kde programs |
| 1265 | 73055 Illegal operand at DXTCV11CompressBlockSSE2 (more SSE opcodes) |
| 1266 | 73026 Descriptor leak check reports port numbers wrongly |
| 1267 | 71705 README_MISSING_SYSCALL_OR_IOCTL out of date |
| 1268 | 72643 Improve support for SSE/SSE2 instructions |
| 1269 | 72484 valgrind leaves it's own signal mask in place when execing |
| 1270 | 72650 Signal Handling always seems to restart system calls |
| 1271 | 72006 The mmap system call turns all errors in ENOMEM |
| 1272 | 71781 gdb attach is pretty useless |
| 1273 | 71180 unhandled instruction bytes: 0xF 0xAE 0x85 0xE8 |
| 1274 | 69886 writes to zero page cause valgrind to assert on exit |
| 1275 | 71791 crash when valgrinding gimp 1.3 (stabs reader problem) |
| 1276 | 69783 unhandled syscall: 218 |
| 1277 | 69782 unhandled instruction bytes: 0x66 0xF 0x2B 0x80 |
| 1278 | 70385 valgrind fails if the soft file descriptor limit is less |
| 1279 | than about 828 |
| 1280 | 69529 "rep; nop" should do a yield |
| 1281 | 70827 programs with lots of shared libraries report "mmap failed" |
| 1282 | for some of them when reading symbols |
| 1283 | 71028 glibc's strnlen is optimised enough to confuse valgrind |
| 1284 | |
| 1285 | |
| 1286 | |
| 1287 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1288 | Unstable (cvs head) release 2.1.0 (15 December 2003) |
| 1289 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1290 | For whatever it's worth, 2.1.0 actually seems pretty darn stable to me |
| 1291 | (Julian). It looks eminently usable, and given that it fixes some |
| 1292 | significant bugs, may well be worth using on a day-to-day basis. |
| 1293 | 2.1.0 is known to build and pass regression tests on: SuSE 9, SuSE |
| 1294 | 8.2, RedHat 8. |
| 1295 | |
| 1296 | 2.1.0 most notably includes Jeremy Fitzhardinge's complete overhaul of |
| 1297 | handling of system calls and signals, and their interaction with |
| 1298 | threads. In general, the accuracy of the system call, thread and |
| 1299 | signal simulations is much improved. Specifically: |
| 1300 | |
| 1301 | - Blocking system calls behave exactly as they do when running |
| 1302 | natively (not on valgrind). That is, if a syscall blocks only the |
| 1303 | calling thread when running natively, than it behaves the same on |
| 1304 | valgrind. No more mysterious hangs because V doesn't know that some |
| 1305 | syscall or other, should block only the calling thread. |
| 1306 | |
| 1307 | - Interrupted syscalls should now give more faithful results. |
| 1308 | |
| 1309 | - Finally, signal contexts in signal handlers are supported. As a |
| 1310 | result, konqueror on SuSE 9 no longer segfaults when notified of |
| 1311 | file changes in directories it is watching. |
| 1312 | |
| 1313 | Other changes: |
| 1314 | |
| 1315 | - Robert Walsh's file descriptor leakage checks. When enabled, |
| 1316 | Valgrind will print out a list of open file descriptors on |
| 1317 | exit. Along with each file descriptor, Valgrind prints out a stack |
| 1318 | backtrace of where the file was opened and any details relating to the |
| 1319 | file descriptor such as the file name or socket details. |
| 1320 | To use, give: --track-fds=yes |
| 1321 | |
| 1322 | - Implemented a few more SSE/SSE2 instructions. |
| 1323 | |
| 1324 | - Less crud on the stack when you do 'where' inside a GDB attach. |
| 1325 | |
| 1326 | - Fixed the following bugs: |
| 1327 | 68360: Valgrind does not compile against 2.6.0-testX kernels |
| 1328 | 68525: CVS head doesn't compile on C90 compilers |
| 1329 | 68566: pkgconfig support (wishlist) |
| 1330 | 68588: Assertion `sz == 4' failed in vg_to_ucode.c (disInstr) |
| 1331 | 69140: valgrind not able to explicitly specify a path to a binary. |
| 1332 | 69432: helgrind asserts encountering a MutexErr when there are |
| 1333 | EraserErr suppressions |
| 1334 | |
jseward | 0b12daf | 2003-12-14 14:35:28 +0000 | [diff] [blame] | 1335 | - Increase the max size of the translation cache from 200k average bbs |
| 1336 | to 300k average bbs. Programs on the size of OOo (680m17) are |
| 1337 | thrashing the cache at the smaller size, creating large numbers of |
| 1338 | retranslations and wasting significant time as a result. |
| 1339 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1340 | |
| 1341 | |
| 1342 | Stable release 2.0.0 (5 Nov 2003) |
| 1343 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1344 | |
| 1345 | 2.0.0 improves SSE/SSE2 support, fixes some minor bugs, and |
| 1346 | improves support for SuSE 9 and the Red Hat "Severn" beta. |
| 1347 | |
| 1348 | - Further improvements to SSE/SSE2 support. The entire test suite of |
| 1349 | the GNU Scientific Library (gsl-1.4) compiled with Intel Icc 7.1 |
| 1350 | 20030307Z '-g -O -xW' now works. I think this gives pretty good |
| 1351 | coverage of SSE/SSE2 floating point instructions, or at least the |
| 1352 | subset emitted by Icc. |
| 1353 | |
| 1354 | - Also added support for the following instructions: |
| 1355 | MOVNTDQ UCOMISD UNPCKLPS UNPCKHPS SQRTSS |
| 1356 | PUSH/POP %{FS,GS}, and PUSH %CS (Nb: there is no POP %CS). |
| 1357 | |
| 1358 | - CFI support for GDB version 6. Needed to enable newer GDBs |
| 1359 | to figure out where they are when using --gdb-attach=yes. |
| 1360 | |
| 1361 | - Fix this: |
| 1362 | mc_translate.c:1091 (memcheck_instrument): Assertion |
| 1363 | `u_in->size == 4 || u_in->size == 16' failed. |
| 1364 | |
| 1365 | - Return an error rather than panicing when given a bad socketcall. |
| 1366 | |
| 1367 | - Fix checking of syscall rt_sigtimedwait(). |
| 1368 | |
| 1369 | - Implement __NR_clock_gettime (syscall 265). Needed on Red Hat Severn. |
| 1370 | |
| 1371 | - Fixed bug in overlap check in strncpy() -- it was assuming the src was 'n' |
| 1372 | bytes long, when it could be shorter, which could cause false |
| 1373 | positives. |
| 1374 | |
| 1375 | - Support use of select() for very large numbers of file descriptors. |
| 1376 | |
| 1377 | - Don't fail silently if the executable is statically linked, or is |
| 1378 | setuid/setgid. Print an error message instead. |
| 1379 | |
| 1380 | - Support for old DWARF-1 format line number info. |
| 1381 | |
| 1382 | |
| 1383 | |
| 1384 | Snapshot 20031012 (12 October 2003) |
| 1385 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1386 | |
| 1387 | Three months worth of bug fixes, roughly. Most significant single |
| 1388 | change is improved SSE/SSE2 support, mostly thanks to Dirk Mueller. |
| 1389 | |
| 1390 | 20031012 builds on Red Hat Fedora ("Severn") but doesn't really work |
| 1391 | (curiosly, mozilla runs OK, but a modest "ls -l" bombs). I hope to |
| 1392 | get a working version out soon. It may or may not work ok on the |
| 1393 | forthcoming SuSE 9; I hear positive noises about it but haven't been |
| 1394 | able to verify this myself (not until I get hold of a copy of 9). |
| 1395 | |
| 1396 | A detailed list of changes, in no particular order: |
| 1397 | |
| 1398 | - Describe --gen-suppressions in the FAQ. |
| 1399 | |
| 1400 | - Syscall __NR_waitpid supported. |
| 1401 | |
| 1402 | - Minor MMX bug fix. |
| 1403 | |
| 1404 | - -v prints program's argv[] at startup. |
| 1405 | |
| 1406 | - More glibc-2.3 suppressions. |
| 1407 | |
| 1408 | - Suppressions for stack underrun bug(s) in the c++ support library |
| 1409 | distributed with Intel Icc 7.0. |
| 1410 | |
| 1411 | - Fix problems reading /proc/self/maps. |
| 1412 | |
| 1413 | - Fix a couple of messages that should have been suppressed by -q, |
| 1414 | but weren't. |
| 1415 | |
| 1416 | - Make Addrcheck understand "Overlap" suppressions. |
| 1417 | |
| 1418 | - At startup, check if program is statically linked and bail out if so. |
| 1419 | |
| 1420 | - Cachegrind: Auto-detect Intel Pentium-M, also VIA Nehemiah |
| 1421 | |
| 1422 | - Memcheck/addrcheck: minor speed optimisations |
| 1423 | |
| 1424 | - Handle syscall __NR_brk more correctly than before. |
| 1425 | |
| 1426 | - Fixed incorrect allocate/free mismatch errors when using |
| 1427 | operator new(unsigned, std::nothrow_t const&) |
| 1428 | operator new[](unsigned, std::nothrow_t const&) |
| 1429 | |
| 1430 | - Support POSIX pthread spinlocks. |
| 1431 | |
| 1432 | - Fixups for clean compilation with gcc-3.3.1. |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 1433 | |
| 1434 | - Implemented more opcodes: |
| 1435 | - push %es |
| 1436 | - push %ds |
| 1437 | - pop %es |
| 1438 | - pop %ds |
| 1439 | - movntq |
| 1440 | - sfence |
| 1441 | - pshufw |
| 1442 | - pavgb |
| 1443 | - ucomiss |
| 1444 | - enter |
daywalker | b18d253 | 2003-09-27 20:15:01 +0000 | [diff] [blame] | 1445 | - mov imm32, %esp |
| 1446 | - all "in" and "out" opcodes |
daywalker | 79aad84 | 2003-09-30 22:58:12 +0000 | [diff] [blame] | 1447 | - inc/dec %esp |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1448 | - A whole bunch of SSE/SSE2 instructions |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 1449 | |
jseward | 4323065 | 2003-12-14 00:14:54 +0000 | [diff] [blame] | 1450 | - Memcheck: don't bomb on SSE/SSE2 code. |
daywalker | 5d945de | 2003-09-26 00:32:53 +0000 | [diff] [blame] | 1451 | |
sewardj | 9023879 | 2003-05-05 00:23:42 +0000 | [diff] [blame] | 1452 | |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 1453 | Snapshot 20030725 (25 July 2003) |
| 1454 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1455 | |
| 1456 | Fixes some minor problems in 20030716. |
| 1457 | |
| 1458 | - Fix bugs in overlap checking for strcpy/memcpy etc. |
| 1459 | |
| 1460 | - Do overlap checking with Addrcheck as well as Memcheck. |
| 1461 | |
| 1462 | - Fix this: |
| 1463 | Memcheck: the `impossible' happened: |
| 1464 | get_error_name: unexpected type |
| 1465 | |
| 1466 | - Install headers needed to compile new skins. |
| 1467 | |
sewardj | e3dd2e0 | 2003-07-27 08:04:48 +0000 | [diff] [blame] | 1468 | - Remove leading spaces and colon in the LD_LIBRARY_PATH / LD_PRELOAD |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 1469 | passed to non-traced children. |
| 1470 | |
sewardj | b9eda95 | 2003-07-26 21:39:05 +0000 | [diff] [blame] | 1471 | - Fix file descriptor leak in valgrind-listener. |
| 1472 | |
sewardj | e3dd2e0 | 2003-07-27 08:04:48 +0000 | [diff] [blame] | 1473 | - Fix longstanding bug in which the allocation point of a |
| 1474 | block resized by realloc was not correctly set. This may |
| 1475 | have caused confusing error messages. |
sewardj | 945f39f | 2003-07-25 21:11:40 +0000 | [diff] [blame] | 1476 | |
| 1477 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 1478 | Snapshot 20030716 (16 July 2003) |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1479 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1480 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 1481 | 20030716 is a snapshot of our current CVS head (development) branch. |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1482 | This is the branch which will become valgrind-2.0. It contains |
| 1483 | significant enhancements over the 1.9.X branch. |
| 1484 | |
| 1485 | Despite this being a snapshot of the CVS head, it is believed to be |
| 1486 | quite stable -- at least as stable as 1.9.6 or 1.0.4, if not more so |
| 1487 | -- and therefore suitable for widespread use. Please let us know asap |
| 1488 | if it causes problems for you. |
| 1489 | |
| 1490 | Two reasons for releasing a snapshot now are: |
| 1491 | |
| 1492 | - It's been a while since 1.9.6, and this snapshot fixes |
| 1493 | various problems that 1.9.6 has with threaded programs |
| 1494 | on glibc-2.3.X based systems. |
| 1495 | |
| 1496 | - So as to make available improvements in the 2.0 line. |
| 1497 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 1498 | Major changes in 20030716, as compared to 1.9.6: |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1499 | |
| 1500 | - More fixes to threading support on glibc-2.3.1 and 2.3.2-based |
| 1501 | systems (SuSE 8.2, Red Hat 9). If you have had problems |
| 1502 | with inconsistent/illogical behaviour of errno, h_errno or the DNS |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 1503 | resolver functions in threaded programs, 20030716 should improve |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1504 | matters. This snapshot seems stable enough to run OpenOffice.org |
| 1505 | 1.1rc on Red Hat 7.3, SuSE 8.2 and Red Hat 9, and that's a big |
| 1506 | threaded app if ever I saw one. |
| 1507 | |
| 1508 | - Automatic generation of suppression records; you no longer |
| 1509 | need to write them by hand. Use --gen-suppressions=yes. |
| 1510 | |
sewardj | 2151180 | 2003-07-22 17:47:42 +0000 | [diff] [blame] | 1511 | - strcpy/memcpy/etc check their arguments for overlaps, when |
| 1512 | running with the Memcheck or Addrcheck skins. |
| 1513 | |
| 1514 | - malloc_usable_size() is now supported. |
| 1515 | |
| 1516 | - new client requests: |
| 1517 | - VALGRIND_COUNT_ERRORS, VALGRIND_COUNT_LEAKS: |
| 1518 | useful with regression testing |
| 1519 | - VALGRIND_NON_SIMD_CALL[0123]: for running arbitrary functions |
| 1520 | on real CPU (use with caution!) |
| 1521 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1522 | - The GDB attach mechanism is more flexible. Allow the GDB to |
| 1523 | be run to be specified by --gdb-path=/path/to/gdb, and specify |
| 1524 | which file descriptor V will read its input from with |
| 1525 | --input-fd=<number>. |
| 1526 | |
sewardj | 2151180 | 2003-07-22 17:47:42 +0000 | [diff] [blame] | 1527 | - Cachegrind gives more accurate results (wasn't tracking instructions in |
| 1528 | malloc() and friends previously, is now). |
| 1529 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1530 | - Complete support for the MMX instruction set. |
| 1531 | |
| 1532 | - Partial support for the SSE and SSE2 instruction sets. Work for this |
| 1533 | is ongoing. About half the SSE/SSE2 instructions are done, so |
| 1534 | some SSE based programs may work. Currently you need to specify |
| 1535 | --skin=addrcheck. Basically not suitable for real use yet. |
| 1536 | |
| 1537 | - Significant speedups (10%-20%) for standard memory checking. |
| 1538 | |
| 1539 | - Fix assertion failure in pthread_once(). |
| 1540 | |
| 1541 | - Fix this: |
| 1542 | valgrind: vg_intercept.c:598 (vgAllRoadsLeadToRome_select): |
| 1543 | Assertion `ms_end >= ms_now' failed. |
| 1544 | |
| 1545 | - Implement pthread_mutexattr_setpshared. |
| 1546 | |
| 1547 | - Understand Pentium 4 branch hints. Also implemented a couple more |
| 1548 | obscure x86 instructions. |
| 1549 | |
| 1550 | - Lots of other minor bug fixes. |
| 1551 | |
sewardj | 626fd89 | 2003-07-16 20:10:26 +0000 | [diff] [blame] | 1552 | - We have a decent regression test system, for the first time. |
| 1553 | This doesn't help you directly, but it does make it a lot easier |
| 1554 | for us to track the quality of the system, especially across |
| 1555 | multiple linux distributions. |
| 1556 | |
| 1557 | You can run the regression tests with 'make regtest' after 'make |
| 1558 | install' completes. On SuSE 8.2 and Red Hat 9 I get this: |
| 1559 | |
| 1560 | == 84 tests, 0 stderr failures, 0 stdout failures == |
| 1561 | |
| 1562 | On Red Hat 8, I get this: |
| 1563 | |
| 1564 | == 84 tests, 2 stderr failures, 1 stdout failure == |
| 1565 | corecheck/tests/res_search (stdout) |
| 1566 | memcheck/tests/sigaltstack (stderr) |
| 1567 | |
| 1568 | sigaltstack is probably harmless. res_search doesn't work |
| 1569 | on R H 8 even running natively, so I'm not too worried. |
| 1570 | |
| 1571 | On Red Hat 7.3, a glibc-2.2.5 system, I get these harmless failures: |
| 1572 | |
| 1573 | == 84 tests, 2 stderr failures, 1 stdout failure == |
| 1574 | corecheck/tests/pth_atfork1 (stdout) |
| 1575 | corecheck/tests/pth_atfork1 (stderr) |
| 1576 | memcheck/tests/sigaltstack (stderr) |
| 1577 | |
| 1578 | You need to run on a PII system, at least, since some tests |
| 1579 | contain P6-specific instructions, and the test machine needs |
| 1580 | access to the internet so that corecheck/tests/res_search |
| 1581 | (a test that the DNS resolver works) can function. |
| 1582 | |
sewardj | 9d916ed | 2003-07-14 23:38:40 +0000 | [diff] [blame] | 1583 | As ever, thanks for the vast amount of feedback :) and bug reports :( |
| 1584 | We may not answer all messages, but we do at least look at all of |
| 1585 | them, and tend to fix the most frequently reported bugs. |
| 1586 | |
| 1587 | |
| 1588 | |
sewardj | 3791882 | 2003-05-05 01:05:09 +0000 | [diff] [blame] | 1589 | Version 1.9.6 (7 May 2003 or thereabouts) |
| 1590 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1591 | |
| 1592 | Major changes in 1.9.6: |
| 1593 | |
| 1594 | - Improved threading support for glibc >= 2.3.2 (SuSE 8.2, |
| 1595 | RedHat 9, to name but two ...) It turned out that 1.9.5 |
| 1596 | had problems with threading support on glibc >= 2.3.2, |
| 1597 | usually manifested by threaded programs deadlocking in system calls, |
| 1598 | or running unbelievably slowly. Hopefully these are fixed now. 1.9.6 |
| 1599 | is the first valgrind which gives reasonable support for |
| 1600 | glibc-2.3.2. Also fixed a 2.3.2 problem with pthread_atfork(). |
| 1601 | |
| 1602 | - Majorly expanded FAQ.txt. We've added workarounds for all |
| 1603 | common problems for which a workaround is known. |
| 1604 | |
| 1605 | Minor changes in 1.9.6: |
| 1606 | |
| 1607 | - Fix identification of the main thread's stack. Incorrect |
| 1608 | identification of it was causing some on-stack addresses to not get |
| 1609 | identified as such. This only affected the usefulness of some error |
| 1610 | messages; the correctness of the checks made is unchanged. |
| 1611 | |
| 1612 | - Support for kernels >= 2.5.68. |
| 1613 | |
| 1614 | - Dummy implementations of __libc_current_sigrtmin, |
| 1615 | __libc_current_sigrtmax and __libc_allocate_rtsig, hopefully |
| 1616 | good enough to keep alive programs which previously died for lack of |
| 1617 | them. |
| 1618 | |
| 1619 | - Fix bug in the VALGRIND_DISCARD_TRANSLATIONS client request. |
| 1620 | |
sewardj | 3d47b79 | 2003-05-05 22:15:35 +0000 | [diff] [blame] | 1621 | - Fix bug in the DWARF2 debug line info loader, when instructions |
| 1622 | following each other have source lines far from each other |
| 1623 | (e.g. with inlined functions). |
| 1624 | |
sewardj | 3791882 | 2003-05-05 01:05:09 +0000 | [diff] [blame] | 1625 | - Debug info reading: read symbols from both "symtab" and "dynsym" |
| 1626 | sections, rather than merely from the one that comes last in the |
| 1627 | file. |
| 1628 | |
| 1629 | - New syscall support: prctl(), creat(), lookup_dcookie(). |
| 1630 | |
| 1631 | - When checking calls to accept(), recvfrom(), getsocketopt(), |
| 1632 | don't complain if buffer values are NULL. |
| 1633 | |
| 1634 | - Try and avoid assertion failures in |
| 1635 | mash_LD_PRELOAD_and_LD_LIBRARY_PATH. |
| 1636 | |
| 1637 | - Minor bug fixes in cg_annotate. |
| 1638 | |
| 1639 | |
| 1640 | |
sewardj | 9023879 | 2003-05-05 00:23:42 +0000 | [diff] [blame] | 1641 | Version 1.9.5 (7 April 2003) |
| 1642 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1643 | |
| 1644 | It occurs to me that it would be helpful for valgrind users to record |
| 1645 | in the source distribution the changes in each release. So I now |
| 1646 | attempt to mend my errant ways :-) Changes in this and future releases |
| 1647 | will be documented in the NEWS file in the source distribution. |
| 1648 | |
| 1649 | Major changes in 1.9.5: |
| 1650 | |
| 1651 | - (Critical bug fix): Fix a bug in the FPU simulation. This was |
| 1652 | causing some floating point conditional tests not to work right. |
| 1653 | Several people reported this. If you had floating point code which |
| 1654 | didn't work right on 1.9.1 to 1.9.4, it's worth trying 1.9.5. |
| 1655 | |
| 1656 | - Partial support for Red Hat 9. RH9 uses the new Native Posix |
| 1657 | Threads Library (NPTL), instead of the older LinuxThreads. |
| 1658 | This potentially causes problems with V which will take some |
| 1659 | time to correct. In the meantime we have partially worked around |
| 1660 | this, and so 1.9.5 works on RH9. Threaded programs still work, |
| 1661 | but they may deadlock, because some system calls (accept, read, |
| 1662 | write, etc) which should be nonblocking, in fact do block. This |
| 1663 | is a known bug which we are looking into. |
| 1664 | |
| 1665 | If you can, your best bet (unfortunately) is to avoid using |
| 1666 | 1.9.5 on a Red Hat 9 system, or on any NPTL-based distribution. |
| 1667 | If your glibc is 2.3.1 or earlier, you're almost certainly OK. |
| 1668 | |
| 1669 | Minor changes in 1.9.5: |
| 1670 | |
| 1671 | - Added some #errors to valgrind.h to ensure people don't include |
| 1672 | it accidentally in their sources. This is a change from 1.0.X |
| 1673 | which was never properly documented. The right thing to include |
| 1674 | is now memcheck.h. Some people reported problems and strange |
| 1675 | behaviour when (incorrectly) including valgrind.h in code with |
| 1676 | 1.9.1 -- 1.9.4. This is no longer possible. |
| 1677 | |
| 1678 | - Add some __extension__ bits and pieces so that gcc configured |
| 1679 | for valgrind-checking compiles even with -Werror. If you |
| 1680 | don't understand this, ignore it. Of interest to gcc developers |
| 1681 | only. |
| 1682 | |
| 1683 | - Removed a pointless check which caused problems interworking |
| 1684 | with Clearcase. V would complain about shared objects whose |
| 1685 | names did not end ".so", and refuse to run. This is now fixed. |
| 1686 | In fact it was fixed in 1.9.4 but not documented. |
| 1687 | |
| 1688 | - Fixed a bug causing an assertion failure of "waiters == 1" |
| 1689 | somewhere in vg_scheduler.c, when running large threaded apps, |
| 1690 | notably MySQL. |
| 1691 | |
| 1692 | - Add support for the munlock system call (124). |
| 1693 | |
| 1694 | Some comments about future releases: |
| 1695 | |
| 1696 | 1.9.5 is, we hope, the most stable Valgrind so far. It pretty much |
| 1697 | supersedes the 1.0.X branch. If you are a valgrind packager, please |
| 1698 | consider making 1.9.5 available to your users. You can regard the |
| 1699 | 1.0.X branch as obsolete: 1.9.5 is stable and vastly superior. There |
| 1700 | are no plans at all for further releases of the 1.0.X branch. |
| 1701 | |
| 1702 | If you want a leading-edge valgrind, consider building the cvs head |
| 1703 | (from SourceForge), or getting a snapshot of it. Current cool stuff |
| 1704 | going in includes MMX support (done); SSE/SSE2 support (in progress), |
| 1705 | a significant (10-20%) performance improvement (done), and the usual |
| 1706 | large collection of minor changes. Hopefully we will be able to |
| 1707 | improve our NPTL support, but no promises. |
| 1708 | |