kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/valgrind/PLIST

300 lines
11 KiB
Text
Raw Normal View History

Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
@comment $NetBSD: PLIST,v 1.8 2015/11/28 20:50:07 wiedi Exp $
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
bin/callgrind_annotate
bin/callgrind_control
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
bin/cg_annotate
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
bin/cg_diff
bin/cg_merge
bin/ms_print
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
bin/valgrind
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
bin/valgrind-di-server
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
bin/valgrind-listener
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
bin/vgdb
include/valgrind/callgrind.h
include/valgrind/config.h
include/valgrind/drd.h
include/valgrind/helgrind.h
include/valgrind/libvex_basictypes.h
Update valgrind to version 3.9.0. Main changes are listed below, full list is available on http://valgrind.org/docs/manual/dist.news.html Release 3.9.0 (31 October 2013) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.9.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, X86/Android, X86/MacOSX 10.7 and AMD64/MacOSX 10.7. Support for MacOSX 10.8 is significantly improved relative to the 3.8.0 release. * ================== PLATFORM CHANGES ================= * Support for MIPS64 LE and BE running Linux. Valgrind has been tested on MIPS64 Debian Squeeze and Debian Wheezy distributions. * Support for MIPS DSP ASE on MIPS32 platforms. * Support for s390x Decimal Floating Point instructions on hosts that have the DFP facility installed. * Support for POWER8 (Power ISA 2.07) instructions * Support for Intel AVX2 instructions. This is available only on 64 bit code. * Initial support for Intel Transactional Synchronization Extensions, both RTM and HLE. * Initial support for Hardware Transactional Memory on POWER. * Improved support for MacOSX 10.8 (64-bit only). Memcheck can now run large GUI apps tolerably well. * ==================== TOOL CHANGES ==================== * Memcheck: - Improvements in handling of vectorised code, leading to significantly fewer false error reports. You need to use the flag --partial-loads-ok=yes to get the benefits of these changes. - Better control over the leak checker. It is now possible to specify which leak kinds (definite/indirect/possible/reachable) should be displayed, which should be regarded as errors, and which should be suppressed by a given leak suppression. This is done using the options --show-leak-kinds=kind1,kind2,.., --errors-for-leak-kinds=kind1,kind2,.. and an optional "match-leak-kinds:" line in suppression entries, respectively. Note that generated leak suppressions contain this new line and are therefore more specific than in previous releases. To get the same behaviour as previous releases, remove the "match-leak-kinds:" line from generated suppressions before using them. - Reduced "possible leak" reports from the leak checker by the use of better heuristics. The available heuristics provide detection of valid interior pointers to std::stdstring, to new[] allocated arrays with elements having destructors and to interior pointers pointing to an inner part of a C++ object using multiple inheritance. They can be selected individually using the option --leak-check-heuristics=heur1,heur2,... - Better control of stacktrace acquisition for heap-allocated blocks. Using the --keep-stacktraces option, it is possible to control independently whether a stack trace is acquired for each allocation and deallocation. This can be used to create better "use after free" errors or to decrease Valgrind's resource consumption by recording less information. - Better reporting of leak suppression usage. The list of used suppressions (shown when the -v option is given) now shows, for each leak suppressions, how many blocks and bytes it suppressed during the last leak search. * Helgrind: - False errors resulting from the use of statically initialised mutexes and condition variables (PTHREAD_MUTEX_INITIALISER, etc) have been removed. - False errors resulting from the use of pthread_cond_waits that timeout, have been removed. * ==================== OTHER CHANGES ==================== * Some attempt to tune Valgrind's space requirements to the expected capabilities of the target: - The default size of the translation cache has been reduced from 8 sectors to 6 on Android platforms, since each sector occupies about 40MB when using Memcheck. - The default size of the translation cache has been increased to 16 sectors on all other platforms, reflecting the fact that large applications require instrumentation and storage of huge amounts of code. For similar reasons, the number of memory mapped segments that can be tracked has been increased by a factor of 6. - In all cases, the maximum number of sectors in the translation cache can be controlled by the new flag --num-transtab-sectors. * Changes in how debug info (line numbers, etc) is read: - Valgrind no longer temporarily mmaps the entire object to read from it. Instead, reading is done through a small fixed sized buffer. This avoids virtual memory usage spikes when Valgrind reads debuginfo from large shared objects. - A new experimental remote debug info server. Valgrind can read debug info from a different machine (typically, a build host) where debuginfo objects are stored. This can save a lot of time and hassle when running Valgrind on resource-constrained targets (phones, tablets) when the full debuginfo objects are stored somewhere else. This is enabled by the --debuginfo-server= option. - Consistency checking between main and debug objects can be disabled using the --allow-mismatched-debuginfo option. * Stack unwinding by stack scanning, on ARM. Unwinding by stack scanning can recover stack traces in some cases when the normal unwind mechanisms fail. Stack scanning is best described as "a nasty, dangerous and misleading hack" and so is disabled by default. Use --unw-stack-scan-thresh and --unw-stack-scan-frames to enable and control it. * Detection and merging of recursive stack frame cycles. When your program has recursive algorithms, this limits the memory used by Valgrind for recorded stack traces and avoids recording uninteresting repeated calls. This is controlled by the command line option --merge-recursive-frame and by the monitor command "v.set merge-recursive-frames". * File name and line numbers for used suppressions. The list of used suppressions (shown when the -v option is given) now shows, for each used suppression, the file name and line number where the suppression is defined. * New and modified GDB server monitor features: - valgrind.h has a new client request, VALGRIND_MONITOR_COMMAND, that can be used to execute gdbserver monitor commands from the client program. - A new monitor command, "v.info open_fds", that gives the list of open file descriptors and additional details. - An optional message in the "v.info n_errs_found" monitor command, for example "v.info n_errs_found test 1234 finished", allowing a comment string to be added to the process output, perhaps for the purpose of separating errors of different tests or test phases. - A new monitor command "v.info execontext" that shows information about the stack traces recorded by Valgrind. - A new monitor command "v.do expensive_sanity_check_general" to run some internal consistency checks. * New flag --sigill-diagnostics to control whether a diagnostic message is printed when the JIT encounters an instruction it can't translate. The actual behavior -- delivery of SIGILL to the application -- is unchanged. * The maximum amount of memory that Valgrind can use on 64 bit targets has been increased from 32GB to 64GB. This should make it possible to run applications on Memcheck that natively require up to about 35GB.
2013-11-05 18:49:52 +01:00
include/valgrind/libvex_emnote.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/libvex_guest_amd64.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/libvex_guest_arm64.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/libvex_guest_arm.h
include/valgrind/libvex_guest_mips32.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/libvex_guest_mips64.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/libvex_guest_offsets.h
include/valgrind/libvex_guest_ppc32.h
include/valgrind/libvex_guest_ppc64.h
include/valgrind/libvex_guest_s390x.h
include/valgrind/libvex_guest_x86.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/libvex_guest_tilegx.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/libvex.h
include/valgrind/libvex_ir.h
include/valgrind/libvex_s390x_common.h
include/valgrind/libvex_trc_values.h
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
include/valgrind/memcheck.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/pub_tool_addrinfo.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/pub_tool_aspacehl.h
include/valgrind/pub_tool_aspacemgr.h
include/valgrind/pub_tool_basics_asm.h
include/valgrind/pub_tool_basics.h
include/valgrind/pub_tool_clientstate.h
include/valgrind/pub_tool_clreq.h
include/valgrind/pub_tool_debuginfo.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/pub_tool_deduppoolalloc.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/pub_tool_errormgr.h
include/valgrind/pub_tool_execontext.h
include/valgrind/pub_tool_gdbserver.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/pub_tool_guest.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/pub_tool_hashtable.h
include/valgrind/pub_tool_libcassert.h
include/valgrind/pub_tool_libcbase.h
include/valgrind/pub_tool_libcfile.h
include/valgrind/pub_tool_libcprint.h
include/valgrind/pub_tool_libcproc.h
include/valgrind/pub_tool_libcsetjmp.h
include/valgrind/pub_tool_libcsignal.h
include/valgrind/pub_tool_machine.h
include/valgrind/pub_tool_mallocfree.h
include/valgrind/pub_tool_options.h
include/valgrind/pub_tool_oset.h
include/valgrind/pub_tool_poolalloc.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/pub_tool_rangemap.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/pub_tool_redir.h
include/valgrind/pub_tool_replacemalloc.h
include/valgrind/pub_tool_seqmatch.h
include/valgrind/pub_tool_signals.h
include/valgrind/pub_tool_sparsewa.h
include/valgrind/pub_tool_stacktrace.h
include/valgrind/pub_tool_threadstate.h
include/valgrind/pub_tool_tooliface.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/pub_tool_transtab.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/pub_tool_vki.h
include/valgrind/pub_tool_vkiscnums_asm.h
include/valgrind/pub_tool_vkiscnums.h
include/valgrind/pub_tool_wordfm.h
include/valgrind/pub_tool_xarray.h
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
include/valgrind/valgrind.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-amd64-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-arm64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-arm-linux.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/vki/vki-darwin.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-linux-drm.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-linux.h
include/valgrind/vki/vki-mips32-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-mips64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-posixtypes-amd64-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-posixtypes-arm64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-posixtypes-arm-linux.h
include/valgrind/vki/vki-posixtypes-mips32-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-posixtypes-mips64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-posixtypes-ppc32-linux.h
include/valgrind/vki/vki-posixtypes-ppc64-linux.h
include/valgrind/vki/vki-posixtypes-s390x-linux.h
include/valgrind/vki/vki-posixtypes-x86-linux.h
include/valgrind/vki/vki-ppc32-linux.h
include/valgrind/vki/vki-ppc64-linux.h
include/valgrind/vki/vki-s390x-linux.h
include/valgrind/vki/vki-scnums-amd64-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-scnums-arm64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-scnums-arm-linux.h
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
include/valgrind/vki/vki-scnums-darwin.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-scnums-mips32-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-scnums-mips64-linux.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-scnums-ppc32-linux.h
include/valgrind/vki/vki-scnums-ppc64-linux.h
include/valgrind/vki/vki-scnums-s390x-linux.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/vki/vki-scnums-solaris.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-scnums-x86-linux.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/vki/vki-solaris-repcache.h
include/valgrind/vki/vki-solaris.h
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
include/valgrind/vki/vki-x86-linux.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-xen-domctl.h
include/valgrind/vki/vki-xen-evtchn.h
include/valgrind/vki/vki-xen-gnttab.h
include/valgrind/vki/vki-xen.h
include/valgrind/vki/vki-xen-hvm.h
include/valgrind/vki/vki-xen-memory.h
include/valgrind/vki/vki-xen-mmuext.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/vki/vki-xen-physdev.h
include/valgrind/vki/vki-xen-schedop.h
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
include/valgrind/vki/vki-xen-sysctl.h
include/valgrind/vki/vki-xen-tmem.h
include/valgrind/vki/vki-xen-version.h
include/valgrind/vki/vki-xen-x86.h
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
include/valgrind/vki/vki-xen-xsm.h
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
lib/pkgconfig/valgrind.pc
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/32bit-core-valgrind-s1.xml
lib/valgrind/32bit-core-valgrind-s2.xml
lib/valgrind/32bit-core.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/32bit-linux-valgrind-s1.xml
lib/valgrind/32bit-linux-valgrind-s2.xml
lib/valgrind/32bit-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/32bit-sse-valgrind-s1.xml
lib/valgrind/32bit-sse-valgrind-s2.xml
lib/valgrind/32bit-sse.xml
lib/valgrind/64bit-avx-valgrind-s1.xml
lib/valgrind/64bit-avx-valgrind-s2.xml
lib/valgrind/64bit-avx.xml
lib/valgrind/64bit-core-valgrind-s1.xml
lib/valgrind/64bit-core-valgrind-s2.xml
lib/valgrind/64bit-core.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/64bit-linux-valgrind-s1.xml
lib/valgrind/64bit-linux-valgrind-s2.xml
lib/valgrind/64bit-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/64bit-sse-valgrind-s1.xml
lib/valgrind/64bit-sse-valgrind-s2.xml
lib/valgrind/64bit-sse.xml
lib/valgrind/amd64-avx-coresse-valgrind.xml
lib/valgrind/amd64-avx-coresse.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/amd64-avx-linux-valgrind.xml
lib/valgrind/amd64-avx-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/amd64-coresse-valgrind.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/amd64-linux-valgrind.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/arm-core-valgrind-s1.xml
lib/valgrind/arm-core-valgrind-s2.xml
lib/valgrind/arm-core.xml
lib/valgrind/arm-vfpv3-valgrind-s1.xml
lib/valgrind/arm-vfpv3-valgrind-s2.xml
lib/valgrind/arm-vfpv3.xml
lib/valgrind/arm-with-vfpv3-valgrind.xml
lib/valgrind/arm-with-vfpv3.xml
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/cachegrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/callgrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
lib/valgrind/default.supp
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/drd-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/exp-bbv-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/exp-dhat-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/exp-sgcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
lib/valgrind/getoff-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/helgrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/i386-coresse-valgrind.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/i386-linux-valgrind.xml
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/lackey-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/libcoregrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
lib/valgrind/libreplacemalloc_toolpreload-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
lib/valgrind/libvex-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
lib/valgrind/libvexmultiarch-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/massif-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
lib/valgrind/memcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
lib/valgrind/mips64-cp0-valgrind-s1.xml
lib/valgrind/mips64-cp0-valgrind-s2.xml
lib/valgrind/mips64-cp0.xml
lib/valgrind/mips64-cpu-valgrind-s1.xml
lib/valgrind/mips64-cpu-valgrind-s2.xml
lib/valgrind/mips64-cpu.xml
lib/valgrind/mips64-fpu-valgrind-s1.xml
lib/valgrind/mips64-fpu-valgrind-s2.xml
lib/valgrind/mips64-fpu.xml
lib/valgrind/mips64-linux-valgrind.xml
lib/valgrind/mips64-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/mips-cp0-valgrind-s1.xml
lib/valgrind/mips-cp0-valgrind-s2.xml
lib/valgrind/mips-cp0.xml
lib/valgrind/mips-cpu-valgrind-s1.xml
lib/valgrind/mips-cpu-valgrind-s2.xml
lib/valgrind/mips-cpu.xml
lib/valgrind/mips-fpu-valgrind-s1.xml
lib/valgrind/mips-fpu-valgrind-s2.xml
lib/valgrind/mips-fpu.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/mips-linux-valgrind.xml
lib/valgrind/mips-linux.xml
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/none-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/power64-core-valgrind-s1.xml
lib/valgrind/power64-core-valgrind-s2.xml
lib/valgrind/power64-core.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/power64-linux-valgrind-s1.xml
lib/valgrind/power64-linux-valgrind-s2.xml
lib/valgrind/power64-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/power-altivec-valgrind-s1.xml
lib/valgrind/power-altivec-valgrind-s2.xml
lib/valgrind/power-altivec.xml
lib/valgrind/power-core-valgrind-s1.xml
lib/valgrind/power-core-valgrind-s2.xml
lib/valgrind/power-core.xml
lib/valgrind/power-fpu-valgrind-s1.xml
lib/valgrind/power-fpu-valgrind-s2.xml
lib/valgrind/power-fpu.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/power-linux-valgrind-s1.xml
lib/valgrind/power-linux-valgrind-s2.xml
lib/valgrind/power-linux.xml
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
lib/valgrind/powerpc-altivec32l-valgrind.xml
lib/valgrind/powerpc-altivec32l.xml
lib/valgrind/powerpc-altivec64l-valgrind.xml
lib/valgrind/powerpc-altivec64l.xml
lib/valgrind/s390-acr-valgrind-s1.xml
lib/valgrind/s390-acr-valgrind-s2.xml
lib/valgrind/s390-acr.xml
lib/valgrind/s390-fpr-valgrind-s1.xml
lib/valgrind/s390-fpr-valgrind-s2.xml
lib/valgrind/s390-fpr.xml
lib/valgrind/s390x-core64-valgrind-s1.xml
lib/valgrind/s390x-core64-valgrind-s2.xml
lib/valgrind/s390x-core64.xml
lib/valgrind/s390x-generic-valgrind.xml
lib/valgrind/s390x-generic.xml
Remove superfluous usage of ${LOWER_OPSYS} in PLIST.
2012-11-04 06:09:47 +01:00
lib/valgrind/s390x-linux64-valgrind-s1.xml
lib/valgrind/s390x-linux64-valgrind-s2.xml
lib/valgrind/s390x-linux64.xml
Fix PLIST entries on amd64 and i386.
2012-10-14 00:17:35 +02:00
lib/valgrind/vgpreload_core-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_drd-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_exp-dhat-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_exp-sgcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_helgrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_massif-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
lib/valgrind/vgpreload_memcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
man/man1/callgrind_annotate.1
man/man1/callgrind_control.1
man/man1/cg_annotate.1
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
man/man1/cg_diff.1
man/man1/cg_merge.1
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
man/man1/ms_print.1
Initial import of valgrind, currently marked only available for Linux. Valgrind is a suite of tools for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler.
2005-07-21 21:44:30 +02:00
man/man1/valgrind.1
Update devel/valgrind to 3.10.0. For a a list of bugfixes, see http://valgrind.org/docs/manual/dist.news.html. Other changes are listed below. 3.10.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, MIPS32/Android, X86/Android, X86/MacOSX 10.9 and AMD64/MacOSX 10.9. Support for MacOSX 10.8 and 10.9 is significantly improved relative to the 3.9.0 release. * ================== PLATFORM CHANGES ================= * Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port is mostly complete, and is usable, but some SIMD instructions are as yet unsupported. * Support for little-endian variant of the 64-bit POWER architecture. * Support for Android on MIPS32. * Support for 64bit FPU on MIPS32 platforms. * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9. * Configuration for and running on Android targets has changed. See README.android in the source tree for details. * ================== DEPRECATED FEATURES ================= * --db-attach is now deprecated and will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Learn more here: http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver * ==================== TOOL CHANGES ==================== * Memcheck: - Client code can now selectively disable and re-enable reporting of invalid address errors in specific ranges using the new client requests VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE and VALGRIND_ENABLE_ADDR_ERROR_REPORTING_IN_RANGE. - Leak checker: there is a new leak check heuristic called "length64". This is used to detect interior pointers pointing 8 bytes inside a block, on the assumption that the first 8 bytes holds the value "block size - 8". This is used by sqlite3MemMalloc, for example. - Checking of system call parameters: if a syscall parameter (e.g. bind struct sockaddr, sendmsg struct msghdr, ...) has several fields not initialised, an error is now reported for each field. Previously, an error was reported only for the first uninitialised field. - Mismatched alloc/free checking: a new flag --show-mismatched-frees=no|yes [yes] makes it possible to turn off such checks if necessary. * Helgrind: - Improvements to error messages: o Race condition error message involving heap allocated blocks also show the thread number that allocated the raced-on block. o All locks referenced by an error message are now announced. Previously, some error messages only showed the lock addresses. o The message indicating where a lock was first observed now also describes the address/location of the lock. - Helgrind now understands the Ada task termination rules and creates a happens-before relationship between a terminated task and its master. This avoids some false positives and avoids a big memory leak when a lot of Ada tasks are created and terminated. The interceptions are only activated with forthcoming releases of gnatpro >= 7.3.0w-20140611 and gcc >= 5.0. - A new GDB server monitor command "info locks" giving the list of locks, their location, and their status. * Callgrind: - callgrind_control now supports the --vgdb-prefix argument, which is needed if valgrind was started with this same argument. * ==================== OTHER CHANGES ==================== * Unwinding through inlined function calls. Stack unwinding can now make use of Dwarf3 inlined-unwind information if it is available. The practical effect is that inlined calls become visible in stack traces. The suppression matching machinery has been adjusted accordingly. This is controlled by the new option --read-inline-info=yes|no. Currently this is enabled by default only on Linux and Android targets and only for the tools Memcheck, Helgrind and DRD. * Valgrind can now read EXIDX unwind information on 32-bit ARM targets. If an object contains both CFI and EXIDX unwind information, Valgrind will prefer the CFI over the EXIDX. This facilitates unwinding through system libraries on arm-android targets. * Address description logic has been improved and is now common between Memcheck and Helgrind, resulting in better address descriptions for some kinds of error messages. * Error messages about dubious arguments (eg, to malloc or calloc) are output like other errors. This means that they can be suppressed and they have a stack trace. * The C++ demangler has been updated for better C++11 support. * New and modified GDB server monitor features: - Thread local variables/storage (__thread) can now be displayed. - The GDB server monitor command "v.info location <address>" displays information about an address. The information produced depends on the tool and on the options given to valgrind. Possibly, the following are described: global variables, local (stack) variables, allocated or freed blocks, ... - The option "--vgdb-stop-at=event1,event2,..." allows the user to ask the GDB server to stop at the start of program execution, at the end of the program execution and on Valgrind internal errors. - A new monitor command "v.info stats" shows various Valgrind core and tool statistics. - A new monitor command "v.set hostvisibility" allows the GDB server to provide access to Valgrind internal host status/memory. * A new option "--aspace-minaddr=<address>" can in some situations allow the use of more memory by decreasing the address above which Valgrind maps memory. It can also be used to solve address conflicts with system libraries by increasing the default value. See user manual for details. * The amount of memory used by Valgrind to store debug info (unwind info, line number information and symbol data) has been significantly reduced, even though Valgrind now reads more information in order to support unwinding of inlined function calls. * Dwarf3 handling with --read-var-info=yes has been improved: - Ada and C struct containing VLAs no longer cause a "bad DIE" error - Code compiled with -ffunction-sections -fdata-sections -Wl,--gc-sections no longer causes assertion failures. * Improved checking for the --sim-hints= and --kernel-variant= options. Unknown strings are now detected and reported to the user as a usage error. * The semantics of stack start/end boundaries in the valgrind.h VALGRIND_STACK_REGISTER client request has been clarified and documented. The convention is that start and end are respectively the lowest and highest addressable bytes of the stack.
2014-11-07 09:16:45 +01:00
man/man1/valgrind-listener.1
man/man1/vgdb.1
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
share/doc/valgrind/html/bbv-manual.html
share/doc/valgrind/html/cg-manual.html
share/doc/valgrind/html/cl-format.html
share/doc/valgrind/html/cl-manual.html
share/doc/valgrind/html/design-impl.html
share/doc/valgrind/html/dh-manual.html
share/doc/valgrind/html/dist.authors.html
share/doc/valgrind/html/dist.html
share/doc/valgrind/html/dist.news.html
share/doc/valgrind/html/dist.news.old.html
share/doc/valgrind/html/dist.readme-android_emulator.html
share/doc/valgrind/html/dist.readme-android.html
share/doc/valgrind/html/dist.readme-developers.html
share/doc/valgrind/html/dist.readme.html
share/doc/valgrind/html/dist.readme-mips.html
share/doc/valgrind/html/dist.readme-missing.html
share/doc/valgrind/html/dist.readme-packagers.html
share/doc/valgrind/html/dist.readme-s390.html
Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64. Adjust PLIST
2015-11-28 21:50:07 +01:00
share/doc/valgrind/html/dist.readme-solaris.html
Update valgrind from ancient 2.4.0 to the latest 3.8.1. The full list of changes is too big to be listed here, only changes in the current 3.8 are listed below. For a full list for changes see http://valgrind.org/docs/manual/dist.news.html and http://valgrind.org/docs/manual/dist.news.old.html. Release 3.8.1 (19 September 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.1 is a bug fix release. It fixes some assertion failures in 3.8.0 that occur moderately frequently in real use cases, adds support for some missing instructions on ARM, and fixes a deadlock condition on MacOSX. If you package or deliver 3.8.0 for others to use, you might want to consider upgrading to 3.8.1 instead. The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 284004 == 301281 289584 Unhandled instruction: 0xF 0x29 0xE5 (MOVAPS) 295808 amd64->IR: 0xF3 0xF 0xBC 0xC0 (TZCNT) 298281 wcslen causes false(?) uninitialised value warnings 301281 valgrind hangs on OS X when the process calls system() 304035 disInstr(arm): unhandled instruction 0xE1023053 304867 implement MOVBE instruction in x86 mode 304980 Assertion 'lo <= hi' failed in vgModuleLocal_find_rx_mapping 305042 amd64: implement 0F 7F encoding of movq between two registers 305199 ARM: implement QDADD and QDSUB 305321 amd64->IR: 0xF 0xD 0xC (prefetchw) 305513 killed by fatal signal: SIGSEGV 305690 DRD reporting invalid semaphore when sem_trywait fails 305926 Invalid alignment checks for some AVX instructions 306297 disInstr(thumb): unhandled instruction 0xE883 0x000C 306310 3.8.0 release tarball missing some files 306612 RHEL 6 glibc-2.X default suppressions need /lib*/libc-*patterns 306664 vex amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x46 0x66 0xF n-i-bz shmat of a segment > 4Gb does not work n-i-bz simulate_control_c script wrong USR1 signal number on mips n-i-bz vgdb ptrace calls wrong on mips [...] n-i-bz Fixes for more MPI false positives n-i-bz exp-sgcheck's memcpy causes programs to segfault n-i-bz OSX build w/ clang: asserts at startup n-i-bz Incorrect undef'dness prop for Iop_DPBtoBCD and Iop_BCDtoDPB n-i-bz fix a couple of union tag-vs-field mixups n-i-bz OSX: use __NR_poll_nocancel rather than __NR_poll The following bugs were fixed in 3.8.0 but not listed in this NEWS file at the time: 254088 Valgrind should know about UD2 instruction 301280 == 254088 301902 == 254088 304754 NEWS blows TeX's little mind (3.8.1.TEST2: 18 September 2012, vex r2537, valgrind r12994) (3.8.1: 18 September 2012, vex r2537, valgrind r12996) Release 3.8.0 (10 August 2012) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.8.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS/Linux, ARM/Android, X86/Android, X86/MacOSX 10.6/10.7 and AMD64/MacOSX 10.6/10.7. Support for recent distros and toolchain components (glibc 2.16, gcc 4.7) has been added. There is initial support for MacOSX 10.8, but it is not usable for serious work at present. * ================== PLATFORM CHANGES ================= * Support for MIPS32 platforms running Linux. Valgrind has been tested on MIPS32 and MIPS32r2 platforms running different Debian Squeeze and MeeGo distributions. Both little-endian and big-endian cores are supported. The tools Memcheck, Massif and Lackey have been tested and are known to work. See README.mips for more details. * Preliminary support for Android running on x86. * Preliminary (as-yet largely unusable) support for MacOSX 10.8. * Support for Intel AVX instructions and for AES instructions. This support is available only for 64 bit code. * Support for POWER Decimal Floating Point instructions. * ==================== TOOL CHANGES ==================== * Non-libc malloc implementations are now supported. This is useful for tools that replace malloc (Memcheck, Massif, DRD, Helgrind). Using the new option --soname-synonyms, such tools can be informed that the malloc implementation is either linked statically into the executable, or is present in some other shared library different from libc.so. This makes it possible to process statically linked programs, and programs using other malloc libraries, for example TCMalloc or JEMalloc. * For tools that provide their own replacement for malloc et al, the option --redzone-size=<number> allows users to specify the size of the padding blocks (redzones) added before and after each client allocated block. Smaller redzones decrease the memory needed by Valgrind. Bigger redzones increase the chance to detect blocks overrun or underrun. Prior to this change, the redzone size was hardwired to 16 bytes in Memcheck. * Memcheck: - The leak_check GDB server monitor command now can control the maximum nr of loss records to output. - Reduction of memory use for applications allocating many blocks and/or having many partially defined bytes. - Addition of GDB server monitor command 'block_list' that lists the addresses/sizes of the blocks of a leak search loss record. - Addition of GDB server monitor command 'who_points_at' that lists the locations pointing at a block. - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will detect an invalid access of these redzones, by marking them noaccess. Similarly, if a redzone size is given for a memory pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access. This still allows to find some bugs if the user has forgotten to mark the pool superblock noaccess. - Performance of memory leak check has been improved, especially in cases where there are many leaked blocks and/or many suppression rules used to suppress leak reports. - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to more precise analysis, which is important for LLVM/Clang generated code. This is at the cost of somewhat reduced performance. Note there is no change to analysis precision or costs on Linux targets. * DRD: - Added even more facilities that can help finding the cause of a data race, namely the command-line option --ptrace-addr and the macro DRD_STOP_TRACING_VAR(x). More information can be found in the manual. - Fixed a subtle bug that could cause false positive data race reports. * ==================== OTHER CHANGES ==================== * The C++ demangler has been updated so as to work well with C++ compiled by up to at least g++ 4.6. * Tool developers can make replacement/wrapping more flexible thanks to the new option --soname-synonyms. This was reported above, but in fact is very general and applies to all function replacement/wrapping, not just to malloc-family functions. * Round-robin scheduling of threads can be selected, using the new option --fair-sched= yes. Prior to this change, the pipe-based thread serialisation mechanism (which is still the default) could give very unfair scheduling. --fair-sched=yes improves responsiveness of interactive multithreaded applications, and improves repeatability of results from the thread checkers Helgrind and DRD. * For tool developers: support to run Valgrind on Valgrind has been improved. We can now routinely Valgrind on Helgrind or Memcheck. * gdbserver now shows the float shadow registers as integer rather than float values, as the shadow values are mostly used as bit patterns. * Increased limit for the --num-callers command line flag to 500. * Performance improvements for error matching when there are many suppression records in use. * Improved support for DWARF4 debugging information (bug 284184). * Initial support for DWZ compressed Dwarf debug info. * Improved control over the IR optimiser's handling of the tradeoff between performance and precision of exceptions. Specifically, --vex-iropt-precise-memory-exns has been removed and replaced by --vex-iropt-register-updates, with extended functionality. This allows the Valgrind gdbserver to always show up to date register values to GDB. * Modest performance gains through the use of translation chaining for JIT-generated code. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 197914 Building valgrind from svn now requires automake-1.10 203877 increase to 16Mb maximum allowed alignment for memalign et al 219156 Handle statically linked malloc or other malloc lib (e.g. tcmalloc) 247386 make perf does not run all performance tests 270006 Valgrind scheduler unfair 270777 Adding MIPS/Linux port to Valgrind 270796 s390x: Removed broken support for the TS insn 271438 Fix configure for proper SSE4.2 detection 273114 s390x: Support TR, TRE, TROO, TROT, TRTO, and TRTT instructions 273475 Add support for AVX instructions 274078 improved configure logic for mpicc 276993 fix mremap 'no thrash checks' 278313 Fedora 15/x64: err read debug info with --read-var-info=yes flag 281482 memcheck incorrect byte allocation count in realloc() for silly argument 282230 group allocator for small fixed size, use it for MC_Chunk/SEc vbit 283413 Fix wrong sanity check 283671 Robustize alignment computation in LibVEX_Alloc 283961 Adding support for some HCI IOCTLs 284124 parse_type_DIE: confused by: DWARF 4 284864 == 273475 (Add support for AVX instructions) 285219 Too-restrictive constraints for Thumb2 "SP plus/minus register" 285662 (MacOSX): Memcheck needs to replace memcpy/memmove 285725 == 273475 (Add support for AVX instructions) 286261 add wrapper for linux I2C_RDWR ioctl 286270 vgpreload is not friendly to 64->32 bit execs, gives ld.so warnings 286374 Running cachegrind with --branch-sim=yes on 64-bit PowerPC program fails 286384 configure fails "checking for a supported version of gcc" 286497 == 273475 (Add support for AVX instructions) 286596 == 273475 (Add support for AVX instructions) 286917 disInstr(arm): unhandled instruction: QADD (also QSUB) 287175 ARM: scalar VFP fixed-point VCVT instructions not handled 287260 Incorrect conditional jump or move depends on uninitialised value(s) 287301 vex amd64->IR: 0x66 0xF 0x38 0x41 0xC0 0xB8 0x0 0x0 (PHMINPOSUW) 287307 == 273475 (Add support for AVX instructions) 287858 VG_(strerror): unknown error 288298 (MacOSX) unhandled syscall shm_unlink 288995 == 273475 (Add support for AVX instructions) 289470 Loading of large Mach-O thin binaries fails. 289656 == 273475 (Add support for AVX instructions) 289699 vgdb connection in relay mode erroneously closed due to buffer overrun 289823 == 293754 (PCMPxSTRx not implemented for 16-bit characters) 289839 s390x: Provide support for unicode conversion instructions 289939 monitor cmd 'leak_check' with details about leaked or reachable blocks 290006 memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm" 290655 Add support for AESKEYGENASSIST instruction 290719 valgrind-3.7.0 fails with automake-1.11.2 due to"pkglibdir" usage 290974 vgdb must align pages to VKI_SHMLBA (16KB) on ARM 291253 ES register not initialised in valgrind simulation 291568 Fix 3DNOW-related crashes with baseline x86_64 CPU (w patch) 291865 s390x: Support the "Compare Double and Swap" family of instructions 292300 == 273475 (Add support for AVX instructions) 292430 unrecognized instruction in __intel_get_new_mem_ops_cpuid 292493 == 273475 (Add support for AVX instructions) 292626 Missing fcntl F_SETOWN_EX and F_GETOWN_EX support 292627 Missing support for some SCSI ioctls 292628 one/tests/x86/bug125959-x86.c triggers undefined behavior 292841 == 273475 (Add support for AVX instructions) 292993 implement the getcpu syscall on amd64-linux 292995 Implement the “cross memory attach” syscalls introduced in Linux 3.2 293088 Add some VEX sanity checks for ppc64 unhandled instructions 293751 == 290655 (Add support for AESKEYGENASSIST instruction) 293754 PCMPxSTRx not implemented for 16-bit characters 293755 == 293754 (No tests for PCMPxSTRx on 16-bit characters) 293808 CLFLUSH not supported by latest VEX for amd64 294047 valgrind does not correctly emulate prlimit64(..., RLIMIT_NOFILE, ...) 294048 MPSADBW instruction not implemented 294055 regtest none/tests/shell fails when locale is not set to C 294185 INT 0x44 (and others) not supported on x86 guest, but used by Jikes RVM 294190 --vgdb-error=xxx can be out of sync with errors shown to the user 294191 amd64: fnsave/frstor and 0x66 size prefixes on FP instructions 294260 disInstr_AMD64: disInstr miscalculated next %rip 294523 --partial-loads-ok=yes causes false negatives 294617 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A 294736 vex amd64->IR: 0x48 0xF 0xD7 0xD6 0x48 0x83 294812 patch allowing to run (on x86 at least) helgrind/drd on tool. 295089 can not annotate source for both helgrind and drd 295221 POWER Processor decimal floating point instruction support missing 295427 building for i386 with clang on darwin11 requires "-new_linker linker" 295428 coregrind/m_main.c has incorrect x86 assembly for darwin 295590 Helgrind: Assertion 'cvi->nWaiters > 0' failed 295617 ARM - Add some missing syscalls 295799 Missing \n with get_vbits in gdbserver when line is % 80 [...] 296229 Linux user input device ioctls missing wrappers 296318 ELF Debug info improvements (more than one rx/rw mapping) 296422 Add translation chaining support 296457 vex amd64->IR: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A (dup of AES) 296792 valgrind 3.7.0: add SIOCSHWTSTAMP (0x89B0) ioctl wrapper 296983 Fix build issues on x86_64/ppc64 without 32-bit toolchains 297078 gdbserver signal handling problems [..] 297147 drd false positives on newly allocated memory 297329 disallow decoding of IBM Power DFP insns on some machines 297497 POWER Processor decimal floating point instruction support missing 297701 Another alias for strncasecmp_l in libc-2.13.so 297911 'invalid write' not reported when using APIs for custom mem allocators. 297976 s390x: revisit EX implementation 297991 Valgrind interferes with mmap()+ftell() 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux) 297993 Fix compilation of valgrind with gcc -g3. 298080 POWER Processor DFP support missing, part 3 298227 == 273475 (Add support for AVX instructions) 298335 == 273475 (Add support for AVX instructions) 298354 Unhandled ARM Thumb instruction 0xEB0D 0x0585 (streq) 298394 s390x: Don't bail out on an unknown machine model. [..] 298421 accept4() syscall (366) support is missing for ARM 298718 vex amd64->IR: 0xF 0xB1 0xCB 0x9C 0x8F 0x45 298732 valgrind installation problem in ubuntu with kernel version 3.x 298862 POWER Processor DFP instruction support missing, part 4 298864 DWARF reader mis-parses DW_FORM_ref_addr 298943 massif asserts with --pages-as-heap=yes when brk is changing [..] 299053 Support DWARF4 DW_AT_high_pc constant form 299104 == 273475 (Add support for AVX instructions) 299316 Helgrind: hg_main.c:628 (map_threads_lookup): Assertion 'thr' failed. 299629 dup3() syscall (358) support is missing for ARM 299694 POWER Processor DFP instruction support missing, part 5 299756 Ignore --free-fill for MEMPOOL_FREE and FREELIKE client requests 299803 == 273475 (Add support for AVX instructions) 299804 == 273475 (Add support for AVX instructions) 299805 == 273475 (Add support for AVX instructions) 300140 ARM - Missing (T1) SMMUL 300195 == 296318 (ELF Debug info improvements (more than one rx/rw mapping)) 300389 Assertion `are_valid_hwcaps(VexArchAMD64, [..])' failed. 300414 FCOM and FCOMP unimplemented for amd64 guest 301204 infinite loop in canonicaliseSymtab with ifunc symbol 301229 == 203877 (increase to 16Mb maximum allowed alignment for memalign etc) 301265 add x86 support to Android build 301984 configure script doesn't detect certain versions of clang 302205 Fix compiler warnings for POWER VEX code and POWER test cases 302287 Unhandled movbe instruction on Atom processors 302370 PPC: fnmadd, fnmsub, fnmadds, fnmsubs insns always negate the result 302536 Fix for the POWER Valgrind regression test: memcheck-ISA2.0. 302578 Unrecognized isntruction 0xc5 0x32 0xc2 0xca 0x09 vcmpngess 302656 == 273475 (Add support for AVX instructions) 302709 valgrind for ARM needs extra tls support for android emulator [..] 302827 add wrapper for CDROM_GET_CAPABILITY 302901 Valgrind crashes with dwz optimized debuginfo 302918 Enable testing of the vmaddfp and vnsubfp instructions in the testsuite 303116 Add support for the POWER instruction popcntb 303127 Power test suite fixes for frsqrte, vrefp, and vrsqrtefp instructions. 303250 Assertion `instrs_in->arr_used <= 10000' failed w/ OpenSSL code 303466 == 273475 (Add support for AVX instructions) 303624 segmentation fault on Android 4.1 (e.g. on Galaxy Nexus OMAP) 303963 strstr() function produces wrong results under valgrind callgrind 304054 CALL_FN_xx macros need to enforce stack alignment 304561 tee system call not supported 715750 (MacOSX): Incorrect invalid-address errors near 0xFFFFxxxx (mozbug#) n-i-bz Add missing gdbserver xml files for shadow registers for ppc32 n-i-bz Bypass gcc4.4/4.5 code gen bugs causing out of memory or asserts n-i-bz Fix assert in gdbserver for watchpoints watching the same address n-i-bz Fix false positive in sys_clone on amd64 when optional args [..] n-i-bz s390x: Shadow registers can now be examined using vgdb (3.8.0-TEST3: 9 August 2012, vex r2465, valgrind r12865) (3.8.0: 10 August 2012, vex r2465, valgrind r12866)
2012-10-06 14:13:16 +02:00
share/doc/valgrind/html/drd-manual.html
share/doc/valgrind/html/faq.html
share/doc/valgrind/html/FAQ.html
share/doc/valgrind/html/hg-manual.html
share/doc/valgrind/html/images/home.png
share/doc/valgrind/html/images/next.png
share/doc/valgrind/html/images/prev.png
share/doc/valgrind/html/images/up.png
share/doc/valgrind/html/index.html
share/doc/valgrind/html/license.gfdl.html
share/doc/valgrind/html/license.gpl.html
share/doc/valgrind/html/licenses.html
share/doc/valgrind/html/lk-manual.html
share/doc/valgrind/html/manual-core-adv.html
share/doc/valgrind/html/manual-core.html
share/doc/valgrind/html/manual.html
share/doc/valgrind/html/manual-intro.html
share/doc/valgrind/html/manual-writing-tools.html
share/doc/valgrind/html/mc-manual.html
share/doc/valgrind/html/ms-manual.html
share/doc/valgrind/html/nl-manual.html
share/doc/valgrind/html/quick-start.html
share/doc/valgrind/html/QuickStart.html
share/doc/valgrind/html/sg-manual.html
share/doc/valgrind/html/tech-docs.html
share/doc/valgrind/html/vg_basic.css
share/doc/valgrind/valgrind_manual.pdf
share/doc/valgrind/valgrind_manual.ps
Reference in a new issue Copy permalink