The NetBSD Project

CVS log for pkgsrc/devel/valgrind/Makefile

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / devel / valgrind

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.30 / (download) - annotate - [select for diffs], Sun Aug 11 13:20:52 2019 UTC (3 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2019Q3-base, pkgsrc-2019Q3, HEAD
Changes since 1.29: +2 -2 lines
Diff to previous 1.29 (colored)

Bump PKGREVISIONs for perl 5.30.0

Revision 1.29 / (download) - annotate - [select for diffs], Fri Feb 22 23:47:50 2019 UTC (8 months, 2 weeks ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2019Q2-base, pkgsrc-2019Q2, pkgsrc-2019Q1-base, pkgsrc-2019Q1
Changes since 1.28: +2 -2 lines
Diff to previous 1.28 (colored)

Reset maintainership.

Revision 1.28 / (download) - annotate - [select for diffs], Sun Sep 30 11:57:58 2018 UTC (13 months, 1 week ago) by wiedi
Branch: MAIN
CVS Tags: pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3
Changes since 1.27: +2 -1 lines
Diff to previous 1.27 (colored)

valgrind: disable stack-protector and adjust PLIST

Revision 1.27 / (download) - annotate - [select for diffs], Wed Aug 22 09:45:01 2018 UTC (14 months, 3 weeks ago) by wiz
Branch: MAIN
Changes since 1.26: +2 -1 lines
Diff to previous 1.26 (colored)

Recursive bump for perl5-5.28.0

Revision 1.26 / (download) - annotate - [select for diffs], Mon Jan 29 22:35:06 2018 UTC (21 months, 1 week ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1
Changes since 1.25: +4 -4 lines
Diff to previous 1.25 (colored)

Update devel/valgrind to version 3.13.0.

3.13.0 adds support for larger processes and programs, solidifies and improves
support on existing platforms, and provides new heap-use reporting facilities.

      Release 3.13.0 (15 June 2017)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3.13.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, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12.

* ==================== CORE CHANGES ===================

* The translation cache size has been increased to keep up with the demands of
  large applications.  The maximum number of sectors has increased from 24 to
  48.  The default number of sectors has increased from 16 to 32 on all
  targets except Android, where the increase is from 6 to 12.

* The amount of memory that Valgrind can use has been increased from 64GB to
  128GB.  In particular this means your application can allocate up to about
  60GB when running on Memcheck.

* Valgrind's default load address has been changed from 0x3800'0000 to
  0x5800'0000, so as to make it possible to load larger executables.  This
  should make it possible to load executables of size at least 1200MB.

* A massive spaceleak caused by reading compressed debuginfo files has been
  fixed.  Valgrind should now be entirely usable with gcc-7.0 "-gz" created
  debuginfo.

* The C++ demangler has been updated.

* Support for demangling Rust symbols has been added.

* A new representation of stack traces, the "XTree", has been added.  An XTree
  is a tree of stacktraces with data associated with the stacktraces.  This is
  used by various tools (Memcheck, Helgrind, Massif) to report on the heap
  consumption of your program.  Reporting is controlled by the new options
  --xtree-memory=none|allocs|full and --xtree-memory-file=<file>.

  A report can also be produced on demand using the gdbserver monitor command
  'xtmemory [<filename>]>'.  The XTree can be output in 2 formats: 'callgrind
  format' and 'massif format. The existing visualisers for these formats (e.g.
  callgrind_annotate, KCachegrind, ms_print) can be used to visualise and
  analyse these reports.

  Memcheck can also produce XTree leak reports using the Callgrind file
  format.  For more details, see the user manual.

* ================== PLATFORM CHANGES =================

* ppc64: support for ISA 3.0B and various fixes for existing 3.0 support

* amd64: fixes for JIT failure problems on long AVX2 code blocks

* amd64 and x86: support for CET prefixes has been added

* arm32: a few missing ARMv8 instructions have been implemented

* arm64, mips64, mips32: an alternative implementation of Load-Linked and
  Store-Conditional instructions has been added.  This is to deal with
  processor implementations that implement the LL/SC specifications strictly
  and as a result cause Valgrind to hang in certain situations.  The
  alternative implementation is automatically enabled at startup, as required.
  You can use the option --sim-hints=fallback-llsc to force-enable it if you
  want.

* Support for OSX 10.12 has been improved.

* On Linux, clone handling has been improved to honour CLONE_VFORK that
  involves a child stack.  Note however that CLONE_VFORK | CLONE_VM is handled
  like CLONE_VFORK (by removing CLONE_VM), so applications that depend on
  CLONE_VM exact semantics will (still) not work.

* The TileGX/Linux port has been removed because it appears to be both unused
  and unsupported.

* ==================== TOOL CHANGES ====================

* Memcheck:

  - Memcheck should give fewer false positives when running optimised
    Clang/LLVM generated code.

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - New command line options --xtree-leak=no|yes and --xtree-leak-file=<file>
    to produce the end of execution leak report in a xtree callgrind format
    file.

  - New option 'xtleak' in the memcheck leak_check monitor command, to produce
    the leak report in an xtree file.

* Massif:

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - For some workloads (typically, for big applications), Massif memory
    consumption and CPU consumption has decreased significantly.

* Helgrind:

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - addition of client request VALGRIND_HG_GNAT_DEPENDENT_MASTER_JOIN, useful
    for Ada gnat compiled applications.

Revision 1.25 / (download) - annotate - [select for diffs], Sat Sep 16 19:53:51 2017 UTC (2 years, 1 month ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-
Changes since 1.24: +2 -2 lines
Diff to previous 1.24 (colored)

Drop maintainership.

Revision 1.24 / (download) - annotate - [select for diffs], Tue Oct 25 17:41:02 2016 UTC (3 years ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4
Changes since 1.23: +2 -3 lines
Diff to previous 1.23 (colored)

Update devel/valgrind 3.12.0.

Release 3.12.0 (20 October 2016)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.12.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, ARM64/Android,
MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris, X86/MacOSX
10.10 and AMD64/MacOSX 10.10.  There is also preliminary support for
X86/MacOSX 10.11/12, AMD64/MacOSX 10.11/12 and TILEGX/Linux.
* ================== PLATFORM CHANGES =================
* POWER: Support for ISA 3.0 has been added
* mips: support for O32 FPXX ABI has been added.
* mips: improved recognition of different processors
* mips: determination of page size now done at run time
* amd64: Partial support for AMD FMA4 instructions.
* arm, arm64: Support for v8 crypto and CRC instructions.
* Improvements and robustification of the Solaris port.
* Preliminary support for MacOS 10.12 (Sierra) has been added.
Whilst 3.12.0 continues to support the 32-bit x86 instruction set, we
would prefer users to migrate to 64-bit x86 (a.k.a amd64 or x86_64)
where possible.  Valgrind's support for 32-bit x86 has stagnated in
recent years and has fallen far behind that for 64-bit x86
instructions.  By contrast 64-bit x86 is well supported, up to and
including AVX2.
* ==================== TOOL CHANGES ====================
* Memcheck:
  - Added meta mempool support for describing a custom allocator which:
     - Auto-frees all chunks assuming that destroying a pool destroys all
       objects in the pool
     - Uses itself to allocate other memory blocks
  - New flag --ignore-range-below-sp to ignore memory accesses below
    the stack pointer, if you really have to.  The related flag
    --workaround-gcc296-bugs=yes is now deprecated.  Use
    --ignore-range-below-sp=1024-1 as a replacement.
* DRD:
  - Improved thread startup time significantly on non-Linux platforms.
* DHAT
  - Added collection of the metric "tot-blocks-allocd"
* ==================== OTHER CHANGES ====================
* Replacement/wrapping of malloc/new related functions is now done not just
  for system libraries by default, but for any globally defined malloc/new
  related function (both in shared libraries and statically linked alternative
  malloc implementations).  The dynamic (runtime) linker is excluded, though.
  To only intercept malloc/new related functions in
  system libraries use --soname-synonyms=somalloc=nouserintercepts (where
  "nouserintercepts" can be any non-existing library name).
  This new functionality is not implemented for MacOS X.
* The maximum number of callers in a suppression entry is now equal to
  the maximum size for --num-callers (500).
  Note that --gen-suppressions=yes|all similarly generates suppressions
  containing up to --num-callers frames.
* New and modified GDB server monitor features:
  - Valgrind's gdbserver now accepts the command 'catch syscall'.
    Note that you must have GDB >= 7.11 to use 'catch syscall' with
    gdbserver.
* New option --run-cxx-freeres=<yes|no> can be used to change whether
  __gnu_cxx::__freeres() cleanup function is called or not. Default is
  'yes'.
* Valgrind is able to read compressed debuginfo sections in two formats:
  - zlib ELF gABI format with SHF_COMPRESSED flag (gcc option -gz=zlib)
  - zlib GNU format with .zdebug sections (gcc option -gz=zlib-gnu)
* Modest JIT-cost improvements: the cost of instrumenting code blocks
  for the most common use case (x86_64-linux, Memcheck) has been
  reduced by 10%-15%.
* Improved performance for programs that do a lot of discarding of
  instruction address ranges of 8KB or less.
* The C++ symbol demangler has been updated.
* More robustness against invalid syscall parameters on Linux.
* ==================== 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.
191069  Exiting due to signal not reported in XML output
199468  Suppressions: stack size limited to 25
        while --num-callers allows more frames
212352  vex amd64 unhandled opc_aux = 0x 2, first_opcode == 0xDC (FCOM)
278744  cvtps2pd with redundant RexW
303877  valgrind doesn't support compressed debuginfo sections.
345307  Warning about "still reachable" memory when using libstdc++ from gcc 5
348345  Assertion fails for negative lineno
351282  V 3.10.1 MIPS softfloat build broken with GCC 4.9.3 / binutils 2.25.1
351692  Dumps created by valgrind are not readable by gdb (mips32 specific)
351804  Crash on generating suppressions for "printf" call on OS X 10.10
352197  mips: mmap2() not wrapped correctly for page size > 4096
353083  arm64 doesn't implement various xattr system calls
353084  arm64 doesn't support sigpending system call
353137  www: update info for Supported Platforms
353138  www: update "The Valgrind Developers" page
353370  don't advertise RDRAND in cpuid for Core-i7-4910-like avx2 machine
        == 365325
        == 357873
353384  amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x62 (pcmpXstrX $0x62)
353398  WARNING: unhandled amd64-solaris syscall: 207
353660  XML in auxwhat tag not escaping reserved symbols properly
353680  s390x: Crash with certain glibc versions due to non-implemented TBEGIN
353727  amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x72 (pcmpXstrX $0x72)
353802  ELF debug info reader confused with multiple .rodata sections
353891  Assert 'bad_scanned_addr < VG_ROUNDDN(start+len, sizeof(Addr))' failed
353917  unhandled amd64-solaris syscall fchdir(120)
353920  unhandled amd64-solaris syscall: 170
354274  arm: unhandled instruction: 0xEBAD 0x0AC1 (sub.w sl, sp, r1, lsl #3)
354392  unhandled amd64-solaris syscall: 171
354797  Vbit test does not include Iops for Power 8 instruction support
354883  tst->os_state.pthread - magic_delta assertion failure on OSX 10.11
        == 361351
        == 362920
        == 366222
354933  Fix documentation of --kernel-variant=android-no-hw-tls option
355188  valgrind should intercept all malloc related global functions
355454  do not intercept malloc related symbols from the runtime linker
355455  stderr.exp of test cases wrapmalloc and wrapmallocstatic overconstrained
356044  Dwarf line info reader misinterprets is_stmt register
356112  mips: replace addi with addiu
356393  valgrind (vex) crashes because isZeroU happened
        == 363497
        == 364497
356676  arm64-linux: unhandled syscalls 125, 126 (sched_get_priority_max/min)
356678  arm64-linux: unhandled syscall 232 (mincore)
356817  valgrind.h triggers compiler errors on MSVC when defining NVALGRIND
356823  Unsupported ARM instruction: stlex
357059  x86/amd64: SSE cvtpi2ps with memory source does transition to MMX state
357338  Unhandled instruction for SHA instructions libcrypto Boring SSL
357673  crash if I try to run valgrind with a binary link with libcurl
357833  Setting RLIMIT_DATA to zero breaks with linux 4.5+
357871  pthread_spin_destroy not properly wrapped
357887  Calls to VG_(fclose) do not close the file descriptor
357932  amd64->IR: accept redundant REX prefixes for {minsd,maxsd} m128, xmm.
358030  support direct socket calls on x86 32bit (new in linux 4.3)
358478  drd/tests/std_thread.cpp doesn't build with GCC6
359133  Assertion 'eltSzB <= ddpa->poolSzB' failed
359181  Buffer Overflow during Demangling
359201  futex syscall "skips" argument 5 if op is FUTEX_WAIT_BITSET
359289  s390x: popcnt (B9E1) not implemented
359472  The Power PC vsubuqm instruction doesn't always give the correct result
359503  Add missing syscalls for aarch64 (arm64)
359645  "You need libc6-dbg" help message could be more helpful
359703  s390: wire up separate socketcalls system calls
359724  getsockname might crash - deref_UInt should call safe_to_deref
359733  amd64 implement ld.so strchr/index override like x86
359767  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 1/5
359829  Power PC test suite none/tests/ppc64/test_isa_2_07.c uses
        uninitialized data
359838  arm64: Unhandled instruction 0xD5033F5F (clrex)
359871  Incorrect mask handling in ppoll
359952  Unrecognised PCMPESTRM variants (0x70, 0x19)
360008  Contents of Power vr registers contents is not printed correctly when
        the --vgdb-shadow-registers=yes option is used
360035  POWER PC instruction bcdadd and bcdsubtract generate result with
        non-zero shadow bits
360378  arm64: Unhandled instruction 0x5E280844 (sha1h  s4, s2)
360425  arm64 unsupported instruction ldpsw
        == 364435
360519  none/tests/arm64/memory.vgtest might fail with newer gcc
360571  Error about the Android Runtime reading below the stack pointer on ARM
360574  Wrong parameter type for an ashmem ioctl() call on Android and ARM64
360749  kludge for multiple .rodata sections on Solaris no longer needed
360752  raise the number of reserved fds in m_main.c from 10 to 12
361207  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 2/5
361226  s390x: risbgn (EC59) not implemented
361253  [s390x] ex_clone.c:42: undefined reference to `pthread_create'
361354  ppc64[le]: wire up separate socketcalls system calls
361615  Inconsistent termination for multithreaded process terminated by signal
361926  Unhandled Solaris syscall: sysfs(84)
362009  V dumps core on unimplemented functionality before threads are created
362329  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 3/5
362894  missing (broken) support for wbit field on mtfsfi instruction (ppc64)
362935  [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed
362953  Request for an update to the Valgrind Developers page
363680  add renameat2() support
363705  arm64 missing syscall name_to_handle_at and open_by_handle_at
363714  ppc64 missing syscalls sync, waitid and name_to/open_by_handle_at
363858  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 4/5
364058  clarify in manual limitations of array overruns detections
364413  pselect sycallwrapper mishandles NULL sigmask
364728  Power PC, missing support for several HW registers in
        get_otrack_shadow_offset_wrk()
364948  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 5/5
365273  Invalid write to stack location reported after signal handler runs
365912  ppc64BE segfault during jm-insns test (RELRO)
366079  FPXX Support for MIPS32 Valgrind
366138  Fix configure errors out when using Xcode 8 (clang 8.0.0)
366344  Multiple unhandled instruction for Aarch64
        (0x0EE0E020, 0x1AC15800, 0x4E284801, 0x5E040023, 0x5E056060)
367995  Integration of memcheck with custom memory allocator
368120  x86_linux asm _start functions do not keep 16-byte aligned stack pointer
368412  False positive result for altivec capability check
368416  Add tc06_two_races_xml.exp output for ppc64
368419  Perf Events ioctls not implemented
368461  mmapunmap test fails on ppc64
368823  run_a_thread_NORETURN assembly code typo for VGP_arm64_linux target
369000  AMD64 fma4 instructions unsupported.
369169  ppc64 fails jm_int_isa_2_07 test
369175  jm_vec_isa_2_07 test crashes on ppc64
369209  valgrind loops and eats up all memory if cwd doesn't exist.
369356  pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr
369359  msghdr_foreachfield can crash when handling bad iovec
369360  Bad sigprocmask old or new sets can crash valgrind
369361  vmsplice syscall wrapper crashes on bad iovec
369362  Bad sigaction arguments crash valgrind
369383  x86 sys_modify_ldt wrapper crashes on bad ptr
369402  Bad set/get_thread_area pointer crashes valgrind
369441  bad lvec argument crashes process_vm_readv/writev syscall wrappers
369446  valgrind crashes on unknown fcntl command
369439  S390x: Unhandled insns RISBLG/RISBHG and LDE/LDER
369468  Remove quadratic metapool algorithm using VG_(HT_remove_at_Iter)
370265  ISA 3.0 HW cap stuff needs updating
371128  BCD add and subtract instructions on Power BE in 32-bit mode do not work
n-i-bz  Fix incorrect (or infinite loop) unwind on RHEL7 x86 and amd64
n-i-bz  massif --pages-as-heap=yes does not report peak caused by mmap+munmap
n-i-bz  false positive leaks due to aspacemgr merging heap & non heap segments
n-i-bz  Fix ppoll_alarm exclusion on OS X
n-i-bz  Document brk segment limitation, reference manual in limit reached msg.
n-i-bz  Fix clobber list in none/tests/amd64/xacq_xrel.c [valgrind r15737]
n-i-bz  Bump allowed shift value for "add.w reg, sp, reg, lsl #N" [vex r3206]
n-i-bz  amd64: memcheck false positive with shr %edx
n-i-bz  arm3: Allow early writeback of SP base register in "strd rD, [sp, #-16]"
n-i-bz  ppc: Fix two cases of PPCAvFpOp vs PPCFpOp enum confusion
n-i-bz  arm: Fix incorrect register-number constraint check for LDAEX{,B,H,D}
n-i-bz  DHAT: added collection of the metric "tot-blocks-allocd"
(3.12.0.RC1:  20 October 2016, vex r3282, valgrind r16094)
(3.12.0.RC2:  20 October 2016, vex r3282, valgrind r16096)
(3.12.0:      21 October 2016, vex r3282, valgrind r16098)

Revision 1.23 / (download) - annotate - [select for diffs], Sat Jul 9 06:38:13 2016 UTC (3 years, 4 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2016Q3-base, pkgsrc-2016Q3
Changes since 1.22: +2 -1 lines
Diff to previous 1.22 (colored)

Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Revision 1.22 / (download) - annotate - [select for diffs], Sat Jan 16 20:30:11 2016 UTC (3 years, 9 months ago) by ryoon
Branch: MAIN
CVS Tags: pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1
Changes since 1.21: +2 -2 lines
Diff to previous 1.21 (colored)

Adjust HOMEPAGE

Revision 1.21 / (download) - annotate - [select for diffs], Sat Nov 28 20:50:07 2015 UTC (3 years, 11 months ago) by wiedi
Branch: MAIN
CVS Tags: pkgsrc-2015Q4-base, pkgsrc-2015Q4
Changes since 1.20: +3 -2 lines
Diff to previous 1.20 (colored)

Latest valgrind is also for plattform SunOS-*-i386 and SunOS-*-x86_64.
Adjust PLIST

Revision 1.20 / (download) - annotate - [select for diffs], Sat Nov 28 10:12:57 2015 UTC (3 years, 11 months ago) by alnsn
Branch: MAIN
Changes since 1.19: +2 -3 lines
Diff to previous 1.19 (colored)

Update devel/valgrind to version 3.11.0.

   Release 3.11.0 (22 September 2015)
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   3.11.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, ARM64/Android,
   MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris, X86/MacOSX
   10.10 and AMD64/MacOSX 10.10.  There is also preliminary support for
   X86/MacOSX 10.11, AMD64/MacOSX 10.11 and TILEGX/Linux.
   * ================== PLATFORM CHANGES =================
   * Support for Solaris/x86 and Solaris/amd64 has been added.
   * Preliminary support for Mac OS X 10.11 (El Capitan) has been added.
   * Preliminary support for the Tilera TileGX architecture has been added
   .
   * s390x: It is now required for the host to have the "long displacement
   "
     facility.  The oldest supported machine model is z990.
   * x86: on an SSE2 only host, Valgrind in 32 bit mode now claims to be a
     Pentium 4.  3.10.1 wrongly claimed to be a Core 2, which is SSSE3.
   * The JIT's register allocator is significantly faster, making the JIT
     as a whole somewhat faster, so JIT-intensive activities, for example
     program startup, are modestly faster, around 5%.
   * There have been changes to the default settings of several command
     line flags, as detailed below.
   * Intel AVX2 support is more complete (64 bit targets only).  On AVX2
     capable hosts, the simulated CPUID will now indicate AVX2 support.
   * ==================== TOOL CHANGES ====================
   * Memcheck:
     - The default value for --leak-check-heuristics has been changed from
       "none" to "all". This helps to reduce the number of possibly
       lost blocks, in particular for C++ applications.
     - The default value for --keep-stacktraces has been changed from
       "malloc-then-free" to "malloc-and-free".  This has a small cost in
       memory (one word per malloc-ed block) but allows Memcheck to show t
   he
       3 stacktraces of a dangling reference: where the block was allocate
   d,
       where it was freed, and where it is acccessed after being freed.
     - The default value for --partial-loads-ok has been changed from "no"
    to
       "yes", so as to avoid false positive errors resulting from some kin
   ds
       of vectorised loops.
     - A new monitor command 'xb <addr> <len>' shows the validity bits of
       <len> bytes at <addr>.  The monitor command 'xb' is easier to use
       than get_vbits when you need to associate byte data value with
       their corresponding validity bits.
     - The 'block_list' monitor command has been enhanced:
         o it can print a range of loss records
         o it now accepts an optional argument 'limited <max_blocks>'
           to control the number of blocks printed.
         o if a block has been found using a heuristic, then
           'block_list' now shows the heuristic after the block size.
         o the loss records/blocks to print can be limited to the blocks
           found via specified heuristics.
     - The C helper functions used to instrument loads on
       x86-{linux,solaris} and arm-linux (both 32-bit only) have been
       replaced by handwritten assembly sequences.  This gives speedups
       in the region of 0% to 7% for those targets only.
     - A new command line option, --expensive-definedness-checks=yes|no,
       has been added.  This is useful for avoiding occasional invalid
       uninitialised-value errors in optimised code.  Watch out for
       runtime degradation, as this can be up to 25%.  As always, though,
       the slowdown is highly application specific.  The default setting
       is "no".
   * Massif:
     - A new monitor command 'all_snapshots <filename>' dumps all
       snapshots taken so far.
   * Helgrind:
     - Significant memory reduction and moderate speedups for
       --history-level=full for applications accessing a lot of memory
       with many different stacktraces.
     - The default value for --conflict-cache-size=N has been doubled to
       2000000.  Users that were not using the default value should
       preferably also double the value they give.
       The default was changed due to the changes in the "full history"
       implementation.  Doubling the value gives on average a slightly mor
   e
       complete history and uses similar memory (or significantly less mem
   ory
       in the worst case) than the previous implementation.

     - The Helgrind monitor command 'info locks' now accepts an optional
       argument 'lock_addr', which shows information about the lock at the
       given address only.
     - When using --history-level=full, the new Helgrind monitor command
       'accesshistory <addr> [<len>]' will show the recorded accesses for
       <len> (or 1) bytes at <addr>.
   * ==================== OTHER CHANGES ====================
   * The default value for the --smc-check option has been changed from
     "stack" to "all-non-file" on targets that provide automatic D-I
     cache coherence (x86, amd64 and s390x).  The result is to provide,
     by default, transparent support for JIT generated and self-modifying
     code on all targets.
   * Mac OS X only: the default value for the --dsymutil option has been
     changed from "no" to "yes", since any serious usage on Mac OS X
     always required it to be "yes".
   * The command line options --db-attach and --db-command have been remov
   ed.
     They were deprecated in 3.10.0.
   * When a process dies due to a signal, Valgrind now shows the signal
     and the stacktrace at default verbosity (i.e. verbosity 1).
   * The address description logic used by Memcheck and Helgrind now
     describes addresses in anonymous segments, file mmap-ed segments,
     shared memory segments and the brk data segment.
   * The new option --error-markers=<begin>,<end> can be used to mark the
     begin/end of errors in textual output mode, to facilitate
     searching/extracting errors in output files that mix valgrind errors
     with program output.
   * The new option --max-threads=<number> can be used to change the numbe
   r
     of threads valgrind can handle.  The default is 500 threads which
     should be more than enough for most applications.
   * The new option --valgrind-stacksize=<number> can be used to change th
   e
     size of the private thread stacks used by Valgrind.  This is useful
     for reducing memory use or increasing the stack size if Valgrind
     segfaults due to stack overflow.
   * The new option --avg-transtab-entry-size=<number> can be used to spec
   ify
     the expected instrumented block size, either to reduce memory use or
     to avoid excessive retranslation.
   * Valgrind can be built with Intel's ICC compiler, version 14.0 or late
   r.
   * New and modified GDB server monitor features:
     - When a signal is reported in GDB, you can now use the GDB convenien
   ce
       variable $_siginfo to examine detailed signal information.

     - Valgrind's gdbserver now allows the user to change the signal
       to deliver to the process.  So, use 'signal SIGNAL' to continue exe
   cution
       with SIGNAL instead of the signal reported to GDB. Use 'signal 0' t
   o
       continue without passing the signal to the process.
     - With GDB >= 7.10, the command 'target remote'
       will automatically load the executable file of the process running
       under Valgrind. This means you do not need to specify the executabl
   e
       file yourself, GDB will discover it itself.  See GDB documentation
   about
       'qXfer:exec-file:read' packet for more info.
   * ==================== 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.
   116002  VG_(printf): Problems with justification of strings and integer
   s
   155125  avoid cutting away file:lineno after long function name
   197259  Unsupported arch_prtctl PR_SET_GS option
   201152  ppc64: Assertion in ppc32g_dirtyhelper_MFSPR_268_269
   201216  Fix Valgrind does not support pthread_sigmask() on OS X
   201435  Fix Darwin: -v does not show kernel version
   208217  "Warning: noted but unhandled ioctl 0x2000747b" on Mac OS X
   211256  Fixed an outdated comment regarding the default platform.
   211529  Incomplete call stacks for code compiled by newer versions of M
   SVC
   211926  Avoid compilation warnings in valgrind.h with -pedantic
   212291  Fix unhandled syscall: unix:132 (mkfifo) on OS X
           == 263119
   226609  Crediting upstream authors in man page
   231257  Valgrind omits path when executing script from shebang line
   254164  OS X task_info: UNKNOWN task message [id 3405, to mach_task_sel
   f() [..]
   269360  s390x: Fix addressing mode selection for compare-and-swap
   302630  Memcheck: Assertion failed: 'sizeof(UWord) == sizeof(UInt)'
           == 326797
   312989  ioctl handling needs to do POST handling on generic ioctls and
   [..]
   319274  Fix unhandled syscall: unix:410 (sigsuspend_nocancel) on OS X
   324181  mmap does not handle MAP_32BIT (handle it now, rather than fail
    it)
   327745  Fix valgrind 3.9.0 build fails on Mac OS X 10.6.8
   330147  libmpiwrap PMPI_Get_count returns undefined value
   333051  mmap of huge pages fails due to incorrect alignment
           == 339163
   334802  valgrind does not always explain why a given option is bad
   335618  mov.w rN, pc/sp (ARM32)
   335785  amd64->IR 0xC4 0xE2 0x75 0x2F (vmaskmovpd)
           == 307399
           == 343175
           == 342740
           == 346912
   335907  segfault when running wine's ddrawex/tests/surface.c under valg
   rind
   338602  AVX2 bit in CPUID missing
   338606  Strange message for scripts with invalid interpreter
   338731  ppc: Fix testuite build for toolchains not supporting -maltivec
   338995  shmat with hugepages (SHM_HUGETLB) fails with EINVAL
   339045  Getting valgrind to compile and run on OS X Yosemite (10.10)
           == 340252
   339156  gdbsrv not called for fatal signal
   339215  Valgrind 3.10.0 contain 2013 in copyrights notice
   339288  support Cavium Octeon MIPS specific BBIT*32 instructions
   339636  Use fxsave64 and fxrstor64 mnemonics instead of old-school rex6
   4 prefix
   339442  Fix testsuite build failure on OS X 10.9
   339542  Enable compilation with Intel's ICC compiler
   339563  The DVB demux DMX_STOP ioctl doesn't have a wrapper
   339688  Mac-specific ASM does not support .version directive (cpuid,
           tronical and pushfpopf tests)
   339745  Valgrind crash when check Marmalade app (partial fix)
   339755  Fix known deliberate memory leak in setenv() on Mac OS X 10.9
   339778  Linux/TileGx platform support for Valgrind
   339780  Fix known uninitialised read in pthread_rwlock_init() on Mac OS
    X 10.9
   339789  Fix none/tests/execve test on Mac OS X 10.9
   339808  Fix none/tests/rlimit64_nofile test on Mac OS X 10.9
   339820  vex amd64->IR: 0x66 0xF 0x3A 0x63 0xA 0x42 0x74 0x9 (pcmpistri
   $0x42)
   340115  Fix none/tests/cmdline[1|2] tests on systems which define TMPDI
   R
   340392  Allow user to select more accurate definedness checking in memc
   heck
           to avoid invalid complaints on optimised code
   340430  Fix some grammatical weirdness in the manual.
   341238  Recognize GCC5/DWARFv5 DW_LANG constants (Go, C11, C++11, C++14
   )
   341419  Signal handler ucontext_t not filled out correctly on OS X
   341539  VG_(describe_addr) should not describe address as belonging to
   client
           segment if it is past the heap end
   341613  Enable building of manythreads and thread-exits tests on Mac OS
    X
   341615  Fix none/tests/darwin/access_extended test on Mac OS X
   341698  Valgrind's AESKEYGENASSIST gives wrong result in words 0 and 2
   [..]
   341789  aarch64: shmat fails with valgrind on ARMv8
   341997  MIPS64: Cavium OCTEON insns - immediate operand handled incorre
   ctly
   342008  valgrind.h needs type cast [..] for clang/llvm in 64-bit mode
   342038  Unhandled syscalls on aarch64 (mbind/get/set_mempolicy)
   342063  wrong format specifier for test mcblocklistsearch in gdbserver_
   tests
   342117  Hang when loading PDB file for MSVC compiled Firefox under Wine
   342221  socket connect false positive uninit memory for unknown af fami
   ly
   342353  Allow dumping full massif output while valgrind is still runnin
   g
   342571  Valgrind chokes on AVX compare intrinsic with _CMP_GE_QS
           == 346476
           == 348387
           == 350593
   342603  Add I2C_SMBUS ioctl support
   342635  OS X 10.10 (Yosemite) - missing system calls and fcntl code
   342683  Mark memory past the initial brk limit as unaddressable
   342783  arm: unhandled instruction 0xEEFE1ACA = "vcvt.s32.f32 s3, s3, #
   12"
   342795  Internal glibc __GI_mempcpy call should be intercepted
   342841  s390x: Support instructions fiebr(a) and fidbr(a)
   343012  Unhandled syscall 319 (memfd_create)
   343069  Patch updating v4l2 API support
   343173  helgrind crash during stack unwind
   343219  fix GET_STARTREGS for arm
   343303  Fix known deliberate memory leak in setenv() on Mac OS X 10.10
   343306  OS X 10.10: UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
   343332  Unhandled instruction 0x9E310021 (fcvtmu) on aarch64
   343335  unhandled instruction 0x1E638400 (fccmp) aarch64
   343523  OS X mach_ports_register: UNKNOWN task message [id 3403, to [..
   ]
   343525  OS X host_get_special_port: UNKNOWN host message [id 412, to [.
   .]
   343597  ppc64le: incorrect use of offseof macro
   343649  OS X host_create_mach_voucher: UNKNOWN host message [id 222, to
    [..]
   343663  OS X 10.10  Memchecj always reports a leak regardless of [..]
   343732  Unhandled syscall 144 (setgid) on aarch64
   343733  Unhandled syscall 187 (msgctl and related) on aarch64
   343802  s390x: False positive "conditional jump or move depends on [..]
   343902  --vgdb=yes doesn't break when --xml=yes is used
   343967  Don't warn about setuid/setgid/setcap executable for directorie
   s
   343978  Recognize DWARF5/GCC5 DW_LANG_Fortran 2003 and 2008 constants
   344007  accept4 syscall unhandled on arm64 (242) and ppc64 (344)
   344033  Helgrind on ARM32 loses track of mutex state in pthread_cond_wa
   it
   344054  www - update info for Solaris/illumos
   344416  'make regtest' does not work cleanly on OS X
   344235  Remove duplicate include of pub_core_aspacemgr.h
   344279  syscall sendmmsg on arm64 (269) and ppc32/64 (349) unhandled
   344295  syscall recvmmsg on arm64 (243) and ppc32/64 (343) unhandled
   344307  2 unhandled syscalls on aarch64/arm64: umount2(39), mount (40)
   344314  callgrind_annotate ... warnings about commands containing newli
   nes
   344318  socketcall should wrap recvmmsg and sendmmsg
   344337  Fix unhandled syscall: mach:41 (_kernelrpc_mach_port_guard_trap
   )
   344416  Fix 'make regtest' does not work cleanly on OS X
   344499  Fix compilation for Linux kernel >= 4.0.0
   344512  OS X: unhandled syscall: unix:348 (__pthread_chdir),
           unix:349 (__pthread_fchdir)
   344559  Garbage collection of unused segment names in address space man
   ager
   344560  Fix stack traces missing penultimate frame on OS X
   344621  Fix memcheck/tests/err_disable4 test on OS X
   344686  Fix suppression for pthread_rwlock_init on OS X 10.10
   344702  Fix missing libobjc suppressions on OS X 10.10
           == 344543
   344936  Fix unhandled syscall: unix:473 (readlinkat) on OS X 10.10
   344939  Fix memcheck/tests/xml1 on OS X 10.10
   345016  helgrind/tests/locked_vs_unlocked2 is failing sometimes
   345079  Fix build problems in VEX/useful/test_main.c
   345126  Incorrect handling of VIDIOC_G_AUDIO and G_AUDOUT
   345177  arm64: prfm (reg) not implemented
   345215  Performance improvements for the register allocator
   345248  add support for Solaris OS in valgrind
   345338  TIOCGSERIAL and TIOCSSERIAL ioctl support on Linux
   345394  Fix memcheck/tests/strchr on OS X
   345637  Fix memcheck/tests/sendmsg on OS X
   345695  Add POWERPC support for AT_DCACHESIZE and HWCAP2
   345824  Fix aspacem segment mismatch: seen with none/tests/bigcode
   345887  Fix an assertion in the address space manager
   345928  amd64: callstack only contains current function for small stack
   s
   345984  disInstr(arm): unhandled instruction: 0xEE193F1E
   345987  MIPS64: Implement cavium LHX instruction
   346031  MIPS: Implement support for the CvmCount register (rhwr %0, 31)
   346185  Fix typo saving altivec register v24
   346267  Compiler warnings for PPC64 code on call to LibVEX_GuestPPC64_g
   et_XER()
           and LibVEX_GuestPPC64_get_CR()
   346270  Regression tests none/tests/jm_vec/isa_2_07 and
           none/tests/test_isa_2_07_part2 have failures on PPC64 little en
   dian
   346307  fuse filesystem syscall deadlocks
   346324  PPC64 missing support for lbarx, lharx, stbcx and sthcx instruc
   tions
   346411  MIPS: SysRes::_valEx handling is incorrect
   346416  Add support for LL_IOC_PATH2FID and LL_IOC_GETPARENT Lustre ioc
   tls
   346474  PPC64 Power 8, spr TEXASRU register not supported
   346487  Compiler generates "note" about a future ABI change for PPC64
   346562  MIPS64: lwl/lwr instructions are performing 64bit loads
           and causing spurious "invalid read of size 8" warnings
   346801  Fix link error on OS X: _vgModuleLocal_sf_maybe_extend_stack
   347151  Fix suppression for pthread_rwlock_init on OS X 10.8
   347233  Fix memcheck/tests/strchr on OS X 10.10 (Haswell)
   347322  Power PC regression test cleanup
   347379  valgrind --leak-check=full leak errors from system libs on OS X
    10.8
           == 217236
   347389  unhandled syscall: 373 (Linux ARM syncfs)
   347686  Patch set to cleanup PPC64 regtests
   347978  Remove bash dependencies where not needed
   347982  OS X: undefined symbols for architecture x86_64: "_global" [..]
   347988  Memcheck: the 'impossible' happened: unexpected size for Addr (
   OSX/wine)
           == 345929
   348102  Patch updating v4l2 API support
   348247  amd64 front end: jno jumps wrongly when overflow is not set
   348269  Improve mmap MAP_HUGETLB support.
   348334  (ppc) valgrind does not simulate dcbfl - then my program termin
   ates
   348345  Assertion fails for negative lineno
   348377  Unsupported ARM instruction: yield
   348565  Fix detection of command line option availability for clang
   348574  vex amd64->IR pcmpistri SSE4.2 unsupported (pcmpistri $0x18)
   348728  Fix broken check for VIDIOC_G_ENC_INDEX
   348748  Fix redundant condition
   348890  Fix clang warning about unsupported --param inline-unit-growth=
   900
   348949  Bogus "ERROR: --ignore-ranges: suspiciously large range"
   349034  Add Lustre ioctls LL_IOC_GROUP_LOCK and LL_IOC_GROUP_UNLOCK
   349086  Fix UNKNOWN task message [id 3406, to mach_task_self(), [..]
   349087  Fix UNKNOWN task message [id 3410, to mach_task_self(), [..]
   349626  Implemented additional Xen hypercalls
   349769  Clang/osx: ld: warning: -read_only_relocs cannot be used with x
   86_64
   349790  Clean up of the hardware capability checking utilities.
   349828  memcpy intercepts memmove causing src/dst overlap error (ppc64
   ld.so)
   349874  Fix typos in source code
   349879  memcheck: add handwritten assembly for helperc_LOADV*
   349941  di_notify_mmap might create wrong start/size DebugInfoMapping
   350062  vex x86->IR: 0x66 0xF 0x3A 0xB (ROUNDSD) on OS X
   350202  Add limited param to 'monitor block_list'
   350290  s390x: Support instructions fixbr(a)
   350359  memcheck/tests/x86/fxsave hangs indefinetely on OS X
   350809  Fix none/tests/async-sigs for Solaris
   350811  Remove reference to --db-attach which has been removed.
   350813  Memcheck/x86: enable handwritten assembly helpers for x86/Solar
   is too
   350854  hard-to-understand code in VG_(load_ELF)()
   351140  arm64 syscalls setuid (146) and setresgid (149) not implemented
   351386  Solaris: Cannot run ld.so.1 under Valgrind
   351474  Fix VG_(iseqsigset) as obvious
   351534  Fix incorrect header guard
   351632  Fix UNKNOWN fcntl 97 on OS X 10.11
   351756  Intercept platform_memchr$VARIANT$Haswell on OS X
   351858  ldsoexec support on Solaris
   351873  Newer gcc doesn't allow __builtin_tabortdc[i] in ppc32 mode
   352130  helgrind reports false races for printfs using mempcpy on FILE*
    state
   352284  s390: Conditional jump depends on uninitialised value(s) in vfp
   rintf
   352320  arm64 crash on none/tests/nestedfs
   352765  Vbit test fails on Power 6
   352768  The mbar instruction is missing from the Power PC support
   352769  Power PC program priority register (PPR) is not supported
   n-i-bz  Provide implementations of certain compiler builtins to support
           compilers that may not provide those
   n-i-bz  Old STABS code is still being compiled, but never used. Remove
   it.
   n-i-bz  Fix compilation on distros with glibc < 2.5
   n-i-bz  (vex 3098) Avoid generation of Neon insns on non-Neon hosts
   n-i-bz  Enable rt_sigpending syscall on ppc64 linux.
   n-i-bz  mremap did not work properly on shared memory
   n-i-bz  Fix incorrect sizeof expression in syswrap-xen.c reported by Co
   verity
   n-i-bz  In VALGRIND_PRINTF write out thread name, if any, to xml
   (3.11.0.TEST1:  8 September 2015, vex r3187, valgrind r15646)
   (3.11.0.TEST2: 21 September 2015, vex r3193, valgrind r15667)
   (3.11.0:       22 September 2015, vex r3195, valgrind r15674)

Revision 1.19 / (download) - annotate - [select for diffs], Fri Jun 12 10:50:00 2015 UTC (4 years, 5 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2
Changes since 1.18: +2 -1 lines
Diff to previous 1.18 (colored)

Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Revision 1.18 / (download) - annotate - [select for diffs], Mon Dec 1 10:19:36 2014 UTC (4 years, 11 months ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4
Changes since 1.17: +2 -2 lines
Diff to previous 1.17 (colored)

Update devel/valgrind to 3.10.1.

Release 3.10.1 (25 November 2014)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.10.1 is a bug fix release.  It fixes various bugs reported in 3.10.0
and backports fixes for all reported missing AArch64 ARMv8 instructions
and syscalls from the trunk.  If you package or deliver 3.10.0 for others
to use, you might want to consider upgrading to 3.10.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.

  335440  arm64: ld1 (single structure) is not implemented
  335713  arm64: unhanded instruction: prfm (immediate)
  339020  ppc64: memcheck/tests/ppc64/power_ISA2_05 failing in nightly build
  339182  ppc64: AvSplat ought to load destination vector register with [..]
  339336  PPC64 store quad instruction (stq) is not supposed to change [..]
  339433  ppc64 lxvw4x instruction uses four 32-byte loads
  339645  Use correct tag names in sys_getdents/64 wrappers
  339706  Fix false positive for ioctl(TIOCSIG) on linux
  339721  assertion 'check_sibling == sibling' failed in readdwarf3.c ...
  339853  arm64 times syscall unknown
  339855  arm64 unhandled getsid/setsid syscalls
  339858  arm64 dmb sy not implemented
  339926  Unhandled instruction 0x1E674001 (frintx) on aarm64
  339927  Unhandled instruction 0x9E7100C6 (fcvtmu) on aarch64
  339938  disInstr(arm64): unhandled instruction 0x4F8010A4 (fmla)
	  == 339950
	  339940  arm64: unhandled syscall: 83 (sys_fdatasync) + patch
	  340033  arm64: unhandled insn dmb ishld and some other isb-dmb-dsb variants
	  340028  unhandled syscalls for arm64 (msync, pread64, setreuid and setregid)
	  340036  arm64: Unhandled instruction ld4 (multiple structures, no offset)
	  340236  arm64: unhandled syscalls: mknodat, fchdir, chroot, fchownat
	  340509  arm64: unhandled instruction fcvtas
	  340630  arm64: fchmod (52) and fchown (55) syscalls not recognized
	  340632  arm64: unhandled instruction fcvtas
	  340725  AVX2: Incorrect decoding of vpbroadcast{b,w} reg,reg forms
	  340788  warning: unhandled syscall: 318 (getrandom)
	  340807  disInstr(arm): unhandled instruction: 0xEE989B20
	  340856  disInstr(arm64): unhandled instruction 0x1E634C45 (fcsel)
	  340922  arm64: unhandled getgroups/setgroups syscalls
	  n-i-bz  DRD and Helgrind: Handle Imbe_CancelReservation (clrex on ARM)
	  n-i-bz  Add missing ]] to terminate CDATA.
	  n-i-bz  Glibc versions prior to 2.5 do not define PTRACE_GETSIGINFO
	  n-i-bz  Enable sys_fadvise64_64 on arm32.
	  n-i-bz  Add test cases for all remaining AArch64 SIMD, FP and memory insns.
	  n-i-bz  Add test cases for all known arm64 load/store instructions.
	  n-i-bz  PRE(sys_openat): when checking whether ARG1 == VKI_AT_FDCWD [..]
	  n-i-bz  Add detection of old ppc32 magic instructions from bug 278808.
	  n-i-bz  exp-dhat: Implement missing function "dh_malloc_usable_size".
	  n-i-bz  arm64: Implement "fcvtpu w, s".
	  n-i-bz  arm64: implement ADDP and various others
	  n-i-bz  arm64: Implement {S,U}CVTF (scalar, fixedpt).
	  n-i-bz  arm64: enable FCVT{A,N}S X,S.

	  (3.10.1: 25 November 2014, vex r3026, valgrind r14785)

Revision 1.17 / (download) - annotate - [select for diffs], Fri Nov 7 08:16:45 2014 UTC (5 years ago) by alnsn
Branch: MAIN
Changes since 1.16: +2 -3 lines
Diff to previous 1.16 (colored)

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.

Revision 1.16 / (download) - annotate - [select for diffs], Thu May 29 23:36:30 2014 UTC (5 years, 5 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2
Changes since 1.15: +2 -1 lines
Diff to previous 1.15 (colored)

Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.

Revision 1.15 / (download) - annotate - [select for diffs], Tue Nov 5 17:49:52 2013 UTC (6 years ago) by alnsn
Branch: MAIN
CVS Tags: pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4
Changes since 1.14: +2 -3 lines
Diff to previous 1.14 (colored)

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.

Revision 1.14 / (download) - annotate - [select for diffs], Fri May 31 12:40:57 2013 UTC (6 years, 5 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2
Changes since 1.13: +2 -1 lines
Diff to previous 1.13 (colored)

Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.

Revision 1.13 / (download) - annotate - [select for diffs], Sun Nov 4 05:12:56 2012 UTC (7 years ago) by minskim
Branch: MAIN
CVS Tags: pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4
Changes since 1.12: +3 -2 lines
Diff to previous 1.12 (colored)

Make valgrind build on Darwin.

Revision 1.12 / (download) - annotate - [select for diffs], Wed Oct 31 11:19:52 2012 UTC (7 years ago) by asau
Branch: MAIN
Changes since 1.11: +1 -3 lines
Diff to previous 1.11 (colored)

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Revision 1.11 / (download) - annotate - [select for diffs], Fri Oct 19 23:13:15 2012 UTC (7 years ago) by alnsn
Branch: MAIN
Changes since 1.10: +3 -1 lines
Diff to previous 1.10 (colored)

Add missing bsd.prefs.mk for ${MACHINE_ARCH}.

Revision 1.10 / (download) - annotate - [select for diffs], Sat Oct 13 22:17:35 2012 UTC (7 years, 1 month ago) by alnsn
Branch: MAIN
Changes since 1.9: +18 -2 lines
Diff to previous 1.9 (colored)

Fix PLIST entries on amd64 and i386.

Revision 1.9 / (download) - annotate - [select for diffs], Mon Oct 8 19:42:47 2012 UTC (7 years, 1 month ago) by alnsn
Branch: MAIN
Changes since 1.8: +3 -1 lines
Diff to previous 1.8 (colored)

Add test target.

Revision 1.8 / (download) - annotate - [select for diffs], Sat Oct 6 12:13:16 2012 UTC (7 years, 1 month ago) by alnsn
Branch: MAIN
Changes since 1.7: +3 -4 lines
Diff to previous 1.7 (colored)

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 ãà×Äross 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)

Revision 1.7 / (download) - annotate - [select for diffs], Wed Oct 3 21:55:56 2012 UTC (7 years, 1 month ago) by wiz
Branch: MAIN
Changes since 1.6: +2 -2 lines
Diff to previous 1.6 (colored)

Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Revision 1.6 / (download) - annotate - [select for diffs], Mon Mar 21 08:24:38 2011 UTC (8 years, 7 months ago) by obache
Branch: MAIN
CVS Tags: pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-2011Q1-base, pkgsrc-2011Q1
Changes since 1.5: +4 -1 lines
Diff to previous 1.5 (colored)

* LICENSE=gnu-gpl-v2
* marked as user-destdir installation support.

Revision 1.5 / (download) - annotate - [select for diffs], Sat Sep 13 19:07:31 2008 UTC (11 years, 2 months ago) by dholland
Branch: MAIN
CVS Tags: pkgsrc-2010Q4-base, pkgsrc-2010Q4, pkgsrc-2010Q3-base, pkgsrc-2010Q3, pkgsrc-2010Q2-base, pkgsrc-2010Q2, pkgsrc-2010Q1-base, pkgsrc-2010Q1, pkgsrc-2009Q4-base, pkgsrc-2009Q4, pkgsrc-2009Q3-base, pkgsrc-2009Q3, pkgsrc-2009Q2-base, pkgsrc-2009Q2, pkgsrc-2009Q1-base, pkgsrc-2009Q1, pkgsrc-2008Q4-base, pkgsrc-2008Q4, pkgsrc-2008Q3-base, pkgsrc-2008Q3
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored)

Requires USE_TOOLS+=perl

Revision 1.4 / (download) - annotate - [select for diffs], Sat Mar 4 21:29:30 2006 UTC (13 years, 8 months ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2008Q2-base, pkgsrc-2008Q2, pkgsrc-2008Q1-base, pkgsrc-2008Q1, pkgsrc-2007Q4-base, pkgsrc-2007Q4, pkgsrc-2007Q3-base, pkgsrc-2007Q3, pkgsrc-2007Q2-base, pkgsrc-2007Q2, pkgsrc-2007Q1-base, pkgsrc-2007Q1, pkgsrc-2006Q4-base, pkgsrc-2006Q4, pkgsrc-2006Q3-base, pkgsrc-2006Q3, pkgsrc-2006Q2-base, pkgsrc-2006Q2, pkgsrc-2006Q1-base, pkgsrc-2006Q1, cwrapper, cube-native-xorg-base, cube-native-xorg
Changes since 1.3: +2 -2 lines
Diff to previous 1.3 (colored)

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.

Revision 1.3 / (download) - annotate - [select for diffs], Sun Feb 5 23:08:54 2006 UTC (13 years, 9 months ago) by joerg
Branch: MAIN
Changes since 1.2: +2 -1 lines
Diff to previous 1.2 (colored)

Recursive revision bump / recommended bump for gettext ABI change.

Revision 1.2 / (download) - annotate - [select for diffs], Sun Jul 24 15:53:41 2005 UTC (14 years, 3 months ago) by kristerw
Branch: MAIN
CVS Tags: pkgsrc-2005Q4-base, pkgsrc-2005Q4, pkgsrc-2005Q3-base, pkgsrc-2005Q3
Changes since 1.1: +2 -2 lines
Diff to previous 1.1 (colored)

Correct spelling of "ONLY_FOR_PLATFORM".

Revision 1.1.1.1 / (download) - annotate - [select for diffs] (vendor branch), Thu Jul 21 19:44:30 2005 UTC (14 years, 3 months ago) by jschauma
Branch: TNF
CVS Tags: pkgsrc-base
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)

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.

Revision 1.1 / (download) - annotate - [select for diffs], Thu Jul 21 19:44:30 2005 UTC (14 years, 3 months ago) by jschauma
Branch: MAIN

Initial revision

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb <webmaster@jp.NetBSD.org>