[ 14:43 stas  ]

• 1.36 devel/valgrind/Makefile
• 1.4 devel/valgrind/distinfo
• 1.2 devel/valgrind/files/patch-Makefile.am
• 1.2 devel/valgrind/files/patch-configure.in
• 1.3 devel/valgrind/files/patch-coregrind-vg_proxylwp.c
• 1.3 devel/valgrind/files/patch-coregrind_Makefile.am
• 1.2 devel/valgrind/files/patch-coregrind_vg_signals.c
• 1.4 devel/valgrind/files/patch-coregrind_vg_syscalls.c
• 1.2 devel/valgrind/files/patch-coregrind_vg_unistd.h
• 1.2 devel/valgrind/files/patch-coregrind_vg_unsafe.h

- Update to version 3.5.0.

Feature safe:   yes

[ 00:40 barner  ]

• 1.16 devel/valgrind-snapshot/Makefile
• 1.1 devel/valgrind-snapshot/files/patch-Makefile.am
• 1.3 devel/valgrind-snapshot/files/patch-configure
• 1.1 devel/valgrind-snapshot/files/patch-configure.in
• 1.2 devel/valgrind-snapshot/files/patch-coregrind-vg_signals.c
• 1.1 devel/valgrind-snapshot/files/patch-coregrind_Makefile.am
• 1.1 devel/valgrind-snapshot/files/patch-coregrind_vg_main.c
• 1.1 devel/valgrind-snapshot/files/patch-coregrind_vg_syscalls.c
• 1.5 devel/valgrind-snapshot/pkg-plist
• 1.18 devel/valgrind/Makefile

- Fix on FreeBSD 6 and above: [1] [2]

  Valgrind did not handle the following sysarch calls, and thus crashed
  immediately
    o get_fsbase
    o set_fsbase
    o get_gsbase
    o set_fsbase

- Valgrind no longer dumps core when its client application does. [2]

  Valgrind-snapshot does contain for safing the client's core dump,
  but it does not work (it resulted in a crash) and has therefore been
  disabled.

(Only the first 15 lines of the commit message are shown above )