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.

5 files changed, 47 insertions, 36 deletions

diff --git a/devel/valgrind/Makefile b/devel/valgrind/Makefile
index 0275a1d6cec..b1755da162c 100644
--- a/devel/valgrind/Makefile
+++ b/devel/valgrind/Makefile
@@ -1,8 +1,7 @@
-# $NetBSD: Makefile,v 1.16 2014/05/29 23:36:30 wiz Exp $
+# $NetBSD: Makefile,v 1.17 2014/11/07 08:16:45 alnsn Exp $
 #
 
-DISTNAME=		valgrind-3.9.0
-PKGREVISION=		1
+DISTNAME=		valgrind-3.10.0
 CATEGORIES=		devel
 MASTER_SITES=		http://valgrind.org/downloads/
 EXTRACT_SUFX=		.tar.bz2
diff --git a/devel/valgrind/PLIST b/devel/valgrind/PLIST
index 104bb0a858b..a9bfb6f5a0e 100644
--- a/devel/valgrind/PLIST
+++ b/devel/valgrind/PLIST
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.6 2013/11/05 17:49:52 alnsn Exp $
+@comment $NetBSD: PLIST,v 1.7 2014/11/07 08:16:45 alnsn Exp $
 bin/callgrind_annotate
 bin/callgrind_control
 bin/cg_annotate
@@ -6,6 +6,7 @@ bin/cg_diff
 bin/cg_merge
 bin/ms_print
 bin/valgrind
+bin/valgrind-di-server
 bin/valgrind-listener
 bin/vgdb
 include/valgrind/callgrind.h
@@ -15,8 +16,10 @@ include/valgrind/helgrind.h
 include/valgrind/libvex_basictypes.h
 include/valgrind/libvex_emnote.h
 include/valgrind/libvex_guest_amd64.h
+include/valgrind/libvex_guest_arm64.h
 include/valgrind/libvex_guest_arm.h
 include/valgrind/libvex_guest_mips32.h
+include/valgrind/libvex_guest_mips64.h
 include/valgrind/libvex_guest_offsets.h
 include/valgrind/libvex_guest_ppc32.h
 include/valgrind/libvex_guest_ppc64.h
@@ -27,6 +30,7 @@ include/valgrind/libvex_ir.h
 include/valgrind/libvex_s390x_common.h
 include/valgrind/libvex_trc_values.h
 include/valgrind/memcheck.h
+include/valgrind/pub_tool_addrinfo.h
 include/valgrind/pub_tool_aspacehl.h
 include/valgrind/pub_tool_aspacemgr.h
 include/valgrind/pub_tool_basics_asm.h
@@ -34,6 +38,7 @@ include/valgrind/pub_tool_basics.h
 include/valgrind/pub_tool_clientstate.h
 include/valgrind/pub_tool_clreq.h
 include/valgrind/pub_tool_debuginfo.h
+include/valgrind/pub_tool_deduppoolalloc.h
 include/valgrind/pub_tool_errormgr.h
 include/valgrind/pub_tool_execontext.h
 include/valgrind/pub_tool_gdbserver.h
@@ -50,6 +55,7 @@ include/valgrind/pub_tool_mallocfree.h
 include/valgrind/pub_tool_options.h
 include/valgrind/pub_tool_oset.h
 include/valgrind/pub_tool_poolalloc.h
+include/valgrind/pub_tool_rangemap.h
 include/valgrind/pub_tool_redir.h
 include/valgrind/pub_tool_replacemalloc.h
 include/valgrind/pub_tool_seqmatch.h
@@ -65,13 +71,18 @@ include/valgrind/pub_tool_wordfm.h
 include/valgrind/pub_tool_xarray.h
 include/valgrind/valgrind.h
 include/valgrind/vki/vki-amd64-linux.h
+include/valgrind/vki/vki-arm64-linux.h
 include/valgrind/vki/vki-arm-linux.h
 include/valgrind/vki/vki-darwin.h
+include/valgrind/vki/vki-linux-drm.h
 include/valgrind/vki/vki-linux.h
 include/valgrind/vki/vki-mips32-linux.h
+include/valgrind/vki/vki-mips64-linux.h
 include/valgrind/vki/vki-posixtypes-amd64-linux.h
+include/valgrind/vki/vki-posixtypes-arm64-linux.h
 include/valgrind/vki/vki-posixtypes-arm-linux.h
 include/valgrind/vki/vki-posixtypes-mips32-linux.h
+include/valgrind/vki/vki-posixtypes-mips64-linux.h
 include/valgrind/vki/vki-posixtypes-ppc32-linux.h
 include/valgrind/vki/vki-posixtypes-ppc64-linux.h
 include/valgrind/vki/vki-posixtypes-s390x-linux.h
@@ -80,14 +91,27 @@ 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
+include/valgrind/vki/vki-scnums-arm64-linux.h
 include/valgrind/vki/vki-scnums-arm-linux.h
 include/valgrind/vki/vki-scnums-darwin.h
 include/valgrind/vki/vki-scnums-mips32-linux.h
+include/valgrind/vki/vki-scnums-mips64-linux.h
 include/valgrind/vki/vki-scnums-ppc32-linux.h
 include/valgrind/vki/vki-scnums-ppc64-linux.h
 include/valgrind/vki/vki-scnums-s390x-linux.h
 include/valgrind/vki/vki-scnums-x86-linux.h
 include/valgrind/vki/vki-x86-linux.h
+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
+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
 lib/pkgconfig/valgrind.pc
 lib/valgrind/32bit-core-valgrind-s1.xml
 lib/valgrind/32bit-core-valgrind-s2.xml
@@ -131,6 +155,7 @@ 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}
+lib/valgrind/getoff-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
 lib/valgrind/helgrind-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
 lib/valgrind/i386-coresse-valgrind.xml
 lib/valgrind/i386-linux-valgrind.xml
@@ -140,6 +165,17 @@ lib/valgrind/libreplacemalloc_toolpreload-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
 lib/valgrind/libvex-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.a
 lib/valgrind/massif-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
 lib/valgrind/memcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}
+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
 lib/valgrind/mips-cp0-valgrind-s1.xml
 lib/valgrind/mips-cp0-valgrind-s2.xml
 lib/valgrind/mips-cp0.xml
@@ -198,8 +234,12 @@ lib/valgrind/vgpreload_memcheck-${VGCONF_ARCH_PRI}-${LOWER_OPSYS}.so
 man/man1/callgrind_annotate.1
 man/man1/callgrind_control.1
 man/man1/cg_annotate.1
+man/man1/cg_diff.1
+man/man1/cg_merge.1
 man/man1/ms_print.1
 man/man1/valgrind.1
+man/man1/valgrind-listener.1
+man/man1/vgdb.1
 share/doc/valgrind/html/bbv-manual.html
 share/doc/valgrind/html/cg-manual.html
 share/doc/valgrind/html/cl-format.html
diff --git a/devel/valgrind/distinfo b/devel/valgrind/distinfo
index 6ee56f7f36f..376defe4b13 100644
--- a/devel/valgrind/distinfo
+++ b/devel/valgrind/distinfo
@@ -1,7 +1,5 @@
-$NetBSD: distinfo,v 1.4 2014/06/05 17:35:12 minskim Exp $
+$NetBSD: distinfo,v 1.5 2014/11/07 08:16:45 alnsn Exp $
 
-SHA1 (valgrind-3.9.0.tar.bz2) = 9415e28933de9d6687f993c4bb797e6bd49583f1
-RMD160 (valgrind-3.9.0.tar.bz2) = 57f28a2c5430777b370433b64e21e1312122b285
-Size (valgrind-3.9.0.tar.bz2) = 10003156 bytes
-SHA1 (patch-configure) = 5ab964407645bd28507aa5c4ffadc63dc05782f3
-SHA1 (patch-configure.ac) = 7e19705700c27356c8c0b09c81be88bf6ecfa93b
+SHA1 (valgrind-3.10.0.tar.bz2) = aec0b8cd042ec36c8cce4f6027b98627ab202f26
+RMD160 (valgrind-3.10.0.tar.bz2) = 7b9e258dc6860eb964c264c09f4812f847748eec
+Size (valgrind-3.10.0.tar.bz2) = 10898253 bytes
diff --git a/devel/valgrind/patches/patch-configure b/devel/valgrind/patches/patch-configure
deleted file mode 100644
index cbd29675542..00000000000
--- a/devel/valgrind/patches/patch-configure
+++ /dev/null
@@ -1,13 +0,0 @@
-$NetBSD: patch-configure,v 1.1 2014/06/05 17:35:12 minskim Exp $
-
---- configure.orig	2014-06-05 02:01:35.000000000 +0000
-+++ configure
-@@ -8490,7 +8490,7 @@ CFLAGS=$safe_CFLAGS
- # (Pedantically if the linker is gold then -Ttext is fine, but newer
- # gold versions also support -Ttext-segment. So just assume that unless
- # we can use -Ttext-segment we need to strip the build-id NOTEs.
--if test "x${linker_using_t_text}" == "xyes"; then
-+if test "x${linker_using_t_text}" = "xyes"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: ld -Ttext used, need to strip build-id NOTEs." >&5
- $as_echo "$as_me: ld -Ttext used, need to strip build-id NOTEs." >&6;}
- # does the linker support -Wl,--build-id=none ?  Note, it's
diff --git a/devel/valgrind/patches/patch-configure.ac b/devel/valgrind/patches/patch-configure.ac
deleted file mode 100644
index c949716296b..00000000000
--- a/devel/valgrind/patches/patch-configure.ac
+++ /dev/null
@@ -1,13 +0,0 @@
-$NetBSD: patch-configure.ac,v 1.1 2014/06/05 17:35:12 minskim Exp $
-
---- configure.ac.orig	2013-10-31 23:28:16.000000000 +0000
-+++ configure.ac
-@@ -1834,7 +1834,7 @@ CFLAGS=$safe_CFLAGS
- # (Pedantically if the linker is gold then -Ttext is fine, but newer
- # gold versions also support -Ttext-segment. So just assume that unless
- # we can use -Ttext-segment we need to strip the build-id NOTEs.
--if test "x${linker_using_t_text}" == "xyes"; then
-+if test "x${linker_using_t_text}" = "xyes"; then
- AC_MSG_NOTICE([ld -Ttext used, need to strip build-id NOTEs.])
- # does the linker support -Wl,--build-id=none ?  Note, it's
- # important that we test indirectly via whichever C compiler