History log of /external/valgrind/none/tests/cmdline2.stdout.exp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
ed39800a83baf5bffbe391f3974eb2af0f415f80 21-Jun-2017 Elliott Hughes <enh@google.com> Upgrade to valgrind 3.13.0 (15 June 2017).

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.

* ==================== OTHER CHANGES ====================

* For Valgrind developers: in an outer/inner setup, the outer Valgrind will
append the inner guest stacktrace to the inner host stacktrace. This helps
to investigate the errors reported by the outer, when they are caused by the
inner guest program (such as an inner regtest). See README_DEVELOPERS for
more info.

* To allow fast detection of callgrind files by desktop environments and file
managers, the format was extended to have an optional first line that
uniquely identifies the format ("# callgrind format"). Callgrind creates
this line now, as does the new xtree functionality.

* File name template arguments (such as --log-file, --xtree-memory-file, ...)
have a new %n format letter that is replaced by a sequence number.

* "--version -v" now shows the SVN revision numbers from which Valgrind was
built.

* ==================== 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.

162848 --log-file output isn't split when a program forks
340777 Illegal instruction on mips (ar71xx)
341481 MIPS64: Iop_CmpNE32 triggers false warning on MIPS64 platforms
342040 Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones
to a different stack.
344139 x86 stack-seg overrides, needed by the Wine people
344524 store conditional of guest applications always fail - observed on
Octeon3(MIPS)
348616 Wine/valgrind: noted but unhandled ioctl 0x5390 [..] (DVD_READ_STRUCT)
352395 Please provide SVN revision info in --version -v
352767 Wine/valgrind: noted but unhandled ioctl 0x5307 [..] (CDROMSTOP)
356374 Assertion 'DRD_(g_threadinfo)[tid].pt_threadid !=
INVALID_POSIX_THREADID' failed
358213 helgrind/drd bar_bad testcase hangs or crashes with new glibc pthread
barrier implementation
358697 valgrind.h: Some code remains even when defining NVALGRIND
359202 Add musl libc configure/compile
360415 amd64 instructions ADCX and ADOX are not implemented in VEX
== 372828 (vex amd64->IR: 0x66 0xF 0x3A 0x62 0x4A 0x10)
360429 unhandled ioctl 0x530d with no size/direction hints (CDROMREADMODE1)
362223 assertion failed when .valgrindrc is a directory instead of a file
367543 bt/btc/btr/bts x86/x86_64 instructions are poorly-handled wrt flags
367942 Segfault vgPlain_do_sys_sigaction (m_signals.c:1138)
368507 can't malloc chunks larger than about 34GB
368529 Android arm target link error, missing atexit and pthread_atfork
368863 WARNING: unhandled arm64-linux syscall: 100 (get_robust_list)
368865 WARNING: unhandled arm64-linux syscall: 272 (kcmp)
368868 disInstr(arm64): unhandled instruction 0xD53BE000 = cntfrq_el0 (ARMv8)
368917 WARNING: unhandled arm64-linux syscall: 218 (request_key)
368918 WARNING: unhandled arm64-linux syscall: 127 (sched_rr_get_interval)
368922 WARNING: unhandled arm64-linux syscall: 161 (sethostname)
368924 WARNING: unhandled arm64-linux syscall: 84 (sync_file_range)
368925 WARNING: unhandled arm64-linux syscall: 130 (tkill)
368926 WARNING: unhandled arm64-linux syscall: 97 (unshare)
369459 valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)
370028 Reduce the number of compiler warnings on MIPS platforms
370635 arm64 missing syscall getcpu
371225 Fix order of timer_{gettime,getoverrun,settime} syscalls on arm64
371227 Clean AArch64 syscall table
371412 Rename wrap_sys_shmat to sys_shmat like other wrappers
371471 Valgrind complains about non legit memory leaks on placement new (C++)
371491 handleAddrOverrides() is [incorrect] when ASO prefix is used
371503 disInstr(arm64): unhandled instruction 0xF89F0000
371869 support '%' in symbol Z-encoding
371916 execution tree xtree concept
372120 c++ demangler demangles symbols which are not c++
372185 Support of valgrind on ARMv8 with 32 bit executable
372188 vex amd64->IR: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 (PCMPxSTRx $0x10)
372195 Power PC, xxsel instruction is not always recognized.
372504 Hanging on exit_group
372600 process loops forever when fatal signals are arriving quickly
372794 LibVEX (arm32 front end): 'Assertion szBlg2 <= 3' failed
373046 Stacks registered by core are never deregistered
373069 memcheck/tests/leak_cpp_interior fails with GCC 5.1+
373086 Implement additional Xen hypercalls
373192 Calling posix_spawn in glibc 2.24 completely broken
373488 Support for fanotify API on ARM64 architecture
== 368864 WARNING: unhandled arm64-linux syscall: 262 (fanotify_init)
373555 Rename BBPTR to GSPTR as it denotes guest state pointer only
373938 const IRExpr arguments for matchIRExpr()
374719 some spelling fixes
374963 increase valgrind's load address to prevent mmap failure
375514 valgrind_get_tls_addr() does not work in case of static TLS
375772 +1 error in get_elf_symbol_info() when computing value of 'hi' address
for ML_(find_rx_mapping)()
375806 Test helgrind/tests/tc22_exit_w_lock fails with glibc 2.24
375839 Temporary storage exhausted, with long sequence of vfmadd231ps insns
== 377159 "vex: the `impossible' happened" still present
== 375150 Assertion 'tres.status == VexTransOK' failed
== 378068 valgrind crashes on AVX2 function in FFmpeg
376142 Segfaults on MIPS Cavium Octeon boards
376279 disInstr(arm64): unhandled instruction 0xD50320FF
376455 Solaris: unhandled syscall lgrpsys(180)
376518 Solaris: unhandled fast trap getlgrp(6)
376611 ppc64 and arm64 don't know about prlimit64 syscall
376729 PPC64, remove R2 from the clobber list
== 371668
376956 syswrap of SNDDRV and DRM_IOCTL_VERSION causing some addresses
to be wrongly marked as addressable
377066 Some Valgrind unit tests fail to compile on Ubuntu 16.10 with
PIE enabled by default
377376 memcheck/tests/linux/getregset fails with glibc2.24
377427 PPC64, lxv instruction failing on odd destination register
377478 PPC64: ISA 3.0 setup fixes
377698 Missing memory check for futex() uaddr arg for FUTEX_WAKE
and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET,
and 2 args for FUTEX_TRYLOCK_PI
377717 Fix massive space leak when reading compressed debuginfo sections
377891 Update Xen 4.6 domctl wrappers
377930 fcntl syscall wrapper is missing flock structure check
378524 libvexmultiarch_test regression on s390x and ppc64
378535 Valgrind reports INTERNAL ERROR in execve syscall wrapper
378673 Update libiberty demangler
378931 Add ISA 3.0B additional isnstructions, add OV32, CA32 setting support
379039 syscall wrapper for prctl(PR_SET_NAME) must not check more than 16 bytes
379094 Valgrind reports INTERNAL ERROR in rt_sigsuspend syscall wrapper
379371 UNKNOWN task message [id 3444, to mach_task_self(), reply 0x603]
(task_register_dyld_image_infos)
379372 UNKNOWN task message [id 3447, to mach_task_self(), reply 0x603]
(task_register_dyld_shared_cache_image_info)
379390 unhandled syscall: mach:70 (host_create_mach_voucher_trap)
379473 MIPS: add support for rdhwr cycle counter register
379504 remove TileGX/Linux port
379525 Support more x86 nop opcodes
379838 disAMode(x86): not an addr!
379703 PC ISA 3.0 fixes: stxvx, stxv, xscmpexpdp instructions
379890 arm: unhandled instruction: 0xEBAD 0x1B05 (sub.w fp, sp, r5, lsl #4)
379895 clock_gettime does not execute POST syscall wrapper
379925 PPC64, mtffs does not set the FPCC and C bits in the FPSCR correctly
379966 WARNING: unhandled amd64-linux syscall: 313 (finit_module)
380200 xtree generated callgrind files refer to files without directory name
380202 Assertion failure for cache line size (cls == 64) on aarch64.
380397 s390x: __GI_strcspn() replacement needed
n-i-bz Fix pub_tool_basics.h build issue with g++ 4.4.7.

(3.13.0.RC1: 2 June 2017, vex r3386, valgrind r16434)
(3.13.0.RC2: 9 June 2017, vex r3389, valgrind r16443)
(3.13.0: 14 June 2017, vex r3396, valgrind r16446)

Bug: N/A
Test: manual
Change-Id: Id4498a49f462c3689cbcb35c15f96a8c7e3cea17
/external/valgrind/none/tests/cmdline2.stdout.exp
a0664b9ca67b594bd6f570a61d3301167a24750c 19-Apr-2017 Elliott Hughes <enh@google.com> Upgrade to 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)

Bug: http://b/37470713
Bug: http://b/29251682
Test: ran runtests-arm(64)?.sh and the bug reporter's specific binary (32- and 64-bit)
Change-Id: I43ccbea946d89fc4ae9f355181ac5061d6ce4453
/external/valgrind/none/tests/cmdline2.stdout.exp
4e1d946c86dffc684a6da4215b66f81573512558 01-Sep-2015 iraisr <iraisr@a5019735-40e9-0310-863c-91ae7b9d1cf9> Document that --read-inline-info=yes is the default
even on Solaris for Memcheck, Helgrind and DRD.
n-i-bz


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15613 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
29dd9e62b241efb2c406ed658720e0dd2e68897d 31-Aug-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change the default setting for --dsymutil from =no to =yes, since
in practice it needs to be permanently enabled on OS X. No change
on other platforms.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15603 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
6d9a33803c50c3bd2593169130382facfbd17521 31-Aug-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change the --smc-check default value to =all-non-file.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15601 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
03d49dd544dd1b1c8431a2303b4943e6bb4e1937 21-Aug-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> More copyright date changes for 2015 (fallout from r15577)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15578 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b9749a5a1fcf2ce8dc4a145f6037821f2a4c1252 24-Jul-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove command line options --db-attach and --db-command which were
deprecated in 3.10.0


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15445 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8eb8bab992e3998c33770b0cdb16059a8b918a06 21-Jul-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Bug 345248 - add support for Solaris OS in valgrind

Authors of this port:
Petr Pavlu setup@dagobah.cz
Ivo Raisr ivosh@ivosh.net
Theo Schlossnagle theo@omniti.com



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15426 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
924c852b5883a7b42298dc8c7542116bd9a8a485 15-Mar-2015 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> New Option --avg-transtab-entry-size=<number> can be used to tune
the size of the translation table sectors, either to gain memory
or to avoid too many retranslations.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15016 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
d0720e4a624bdfe7ce2494d690e7a88f986b93c1 12-Mar-2015 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement command line option --valgrind-stacksize=<number>

This allows to decrease memory usage when using many threads,
if no big stacksize is needed by Valgrind.
If needed (e.g. for demangling big c++ symbols), the V stacksize
can be increased.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15004 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
1e802b6a8d0d4b7b630d2a1dd9683c7c889b01a3 13-Feb-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add command line flag --max-threads=<integer> to increase the number of
threads that valgrind can handle. No recompile is needed.
Part of fixing BZ #337869.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14932 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8d47a61e503b69ffbc783717f5faf09d0bbc4723 05-Feb-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Allow the user to specify precise-exception behaviour for translations
made from file-backed mappings (AOT code, basically) that is different
from the default behaviour as specified by --vex-iropt-register-updates.

New flag is --px-file-backed=, with the same possible args as
--vex-iropt-register-updates has.

Add a new flag --px-default, which is a short alias for
--vex-iropt-register-updates.

Add one line of stats output when --stats=yes, showing counts of how
many translations have been made under each of the 4 different PX
optimisation settings.

No user-visible change if you don't use the new flags.

Relies on VEX API change in r3084.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14906 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
7b3d3565c1559b88c67f629bd6613c8b1a89691b 12-Nov-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement Option --error-markers=<begin>,<end>

* This option can be used to mark the begin/end of errors in textual
output mode, to facilitate searching/extracting errors in output files
mixing valgrind errors with program output.

* Use the new option in various existing regtests to test the various
possible usage.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14714 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
2f87090a21801a0e1ef26369172095d5f86318c7 23-Oct-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add --resync-filter to the --help output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14662 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
5d00ec66e9d8510b8dbed896df64acc3c7772504 20-Oct-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix some testcases which implicitly assumed that TMPDIR was either
not set or set to /tmp This is not always true. Fixes BZ 340115.
Patch by rhyskidd@gmail.com.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14643 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
47c6d14dc05ff276692294ebc29070401ab588af 12-Sep-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r14513 from 3_10_BRANCH (Update docs w.r.t. status of
partially-enabled --read-inline-info.)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14520 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
124e56d42ca77510244fedc937057bd291faa039 06-Sep-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rename "--kernel-variant=android-emulator-no-hw-tls" to
"=android-no-hw-tls" per suggestion from Philippe.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14479 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
122f6afaa5c29d933907e21f5a993e072a3c5745 03-Sep-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Slightly change the help text for some options that involve
user-supplied enumeration values.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14447 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
4450a0efab6e08dc7e40a4dfb5dda7214edb557d 03-Sep-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improvements for Android:

* All Linux targets: add minimal ioctl support for the ION_IOC family

* Android targets: change proprietary-ioctl support for GPUs from
being a build-time #define kludge to being controlled by --kernel-variant,
as it should be. Update documentation accordingly.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14440 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
65f1f2de6427ff357cc780d8c7e0b0e819a95def 01-Sep-2014 mjw <mjw@a5019735-40e9-0310-863c-91ae7b9d1cf9> Adjust cmdline expected test output after r14401 BZ#337871.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14405 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9848690cfe9c59a8a92d4be6e5b43c77786066ee 20-Aug-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add option a new sim-hint no-nptl-pthread-stackcache.

Activating this hint using --sim-hints=no-nptl-pthread-stackcache
means the glibc nptl stack cache will be disabled.

Disabling this stack/tls cache avoids helgrind false positive race conditions
errors when using __thread variables.

Note: disabling the stack cache is done by a kludge, dependent on
internal knowledge of glibc code, and using libpthread debug info.
So, this kludge might be broken with newer glibc version.
This has been tested on various platforms and various
glibc versions 2.11, 2.16 and 2.18

To check if the disabling works, you can do:
valgrind --tool=helgrind --sim-hints=no-nptl-pthread-stackcache -d -v ./helgrind/tests/tls_threads |& grep kludge

If you see the below 2 lines, then hopefully the stack cache has been disabled.
--12624-- deactivate nptl pthread stackcache via kludge: found symbol stack_cache_actsize at addr 0x3AF178
--12624:1:sched pthread stack cache size disabling done via kludge




git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14313 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
ec905f7ed1659f2251045114c785659fbb11ea88 17-Aug-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> The attached patch cleanups the clo processing
of clo which are (or should be) 'enum set'.

* pub_tool_options.h : add new macrox VG_USET_CLO and VG_USETX_CLO to
parse an 'enum set' command line option (with or without "all" keyword).

* use VG_USET_CLO for existing enum set clo options:
memcheck --errors-for-leak-kinds, --show-leak-kinds, --leak-check-heuristics
coregrind --vgdb-stop-at

* change --sim-hints and --kernel-variants to enum set
(this allows to detect user typos: currently, a typo in a sim-hint
or kernel variant is silently ignored. Now, an error will be given
to the user)

* The 2 new sets (--sim-hints and --kernel-variants) should not make
use of the 'all' keyword => VG_(parse_enum_set) has a new argument
to enable/disable the use of the "all" keyword.

* The macros defining an 'all enum' set definition was duplicating
all enum values (so addition of a new enum value could easily
give a bug). Removing these macros as they are unused
(to the exception of the leak-kind set).
For this set, the 'all macro' has been replaced by an 'all function',
coded using parse_enum_set parsing the "all" keyword.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14301 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a6efdfaf009a61c5a09a053dd4ccfa8719ffd8d1 24-Jun-2014 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rename --defaultsupp into --default-suppressions as requested by Julian

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14090 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
73e9a01deb2957fe3f3cd9dd0fda77f389c3deb3 22-Jun-2014 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make none/tests/cmdline[12] pass again

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14082 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a0a73939b0398b6608fd6dbde49820ce6530d12c 15-Jun-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> This patch implements the support needed for stacktraces
showing inlined function calls.
See 278972 valgrind stacktraces and suppression do not handle inlined function call debuginfo

Reading the inlined dwarf call info is activated using the new clo
--read-inline-info=yes
Default is currently no but an objective is to optimise the performance
and memory in order to possibly set it on by default.
(see below discussion about performances).

Basically, the patch provides the following pieces:
1. Implement a new dwarf3 reader that reads the inlined call info
2. Some performance improvements done for this new parser, and
on some common code between the new parser and the var info parser.
3. Use the parsed inlined info to produce stacktrace showing inlined calls
4. Use the parsed inlined info in the suppression matching and suppression generation
5. and of course, some reg tests

1. new dwarf3 reader:
---------------------
Two options were possible: add the reading of the inlined info
in the current var info dwarf reader, or add a 2nd reader.
The 2nd approach was preferred, for the following reasons:
The var info reader is slow, memory hungry and quite complex.
Having a separate parsing phase for the inlined information
is simpler/faster when just reading the inlined info.
Possibly, a single parser would be faster when using both
--read-var-info=yes and --read-inline-info=yes.
However, var-info being extremely memory/cpu hungry, it is unlikely
to be used often, and having a separate parsing for inlined info
does in any case make not much difference.
(--read-var-info=yes is also now less interesting thanks to commit
r13991, which provides a fast and low memory "reasonable" location
for an address).

The inlined info parser reads the dwarf info to make calls
to priv_storage.h ML_(addInlInfo).

2. performance optimisations
----------------------------
* the abbrev cache has been improved in revision r14035.
* The new parser skips the non interesting DIEs
(the var-info parser has no logic to skip uninteresting DIEs).
* Some other minor perf optimisation here and there.
In total now, on a big executable, 15 seconds CPU are needed to
create the inlined info (on my slow x86 pentium).

With regards to memory, the dinfo arena:
with inlined info: 172281856/121085952 max/curr mmap'd
without : 157892608/106721280 max/curr mmap'd,
So, basically, inlined information costs about 15Mb of memory for
my big executable (compared to first version of the patch, this is
already using less memory, thanks to the strpool deduppoolalloc.
The needed memory can probably be decreased somewhat more.

3. produce better stack traces
------------------------------
VG_(describe_IP) has a new argument InlIPCursor *iipc which allows
to describe inlined function calls by doing repetitive calls
to describe_IP. See pub_tool_debuginfo.h for a description.

4. suppression generation and matching
--------------------------------------
* suppression generation now also uses an InlIPCursor *iipc
to generate a line for each inlined fn call.

* suppression matching: to allow suppression matching to
match one IP to several function calls in a suppression entry,
the 'inputCompleter' object (that allows to lazily generate
function or object names for a stacktrace when matching
an error with a suppression) has been generalised a little bit
more to also lazily generate the input sequence.
VG_(generic_match) has been updated so as to be more generic
with respect to the input completer : when providing an
input completer, VG_(generic_match) does not need anymore
to produce/compute any input itself : this is all delegated
to the input completer.

5. various regtests
-------------------
to test stack traces with inlined calls, and suppressions
of (some of) these errors using inlined fn calls matching.


Work still to do:
-----------------
* improve parsing performance
* improve the memory overhead.
* handling the directory name for files of the inlined function calls is not yet done.
(probably implies to refactor some code)
* see if m_errormgr.c *offsets arrays cannot be managed via xarray



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14036 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
e4d78123089e55bec64a4f848bdc09556192e259 20-Apr-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> * New option --aspace-minaddr=<address> allows to (possibly) make
use of some more memory by decreasing the default value
or solve some conflicts with system libraries by increasing the value.
See user manual for details.

Note that the lowest accepted possible value is 0x1000, which is
the current value used by Macos in 32bits.
On linux, 0x10000 (64KB) seems to cause not much conflicts.

Default values are unchanged (i.e. are the same as when there
was no clo option).



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13901 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
180a7500bf2464d5b16cddb5618b91fb3f095998 20-Apr-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> - The option "--vgdb-stop-at=event1,event2,..." allows the user
to ask GDB server to stop before program execution, at the end
of the program execution and on Valgrind internal errors.

- A new monitor command "v.set hostvisibility" that allows GDB server
to provide access to Valgrind internal host status/memory.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13900 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0f157ddb404bcde7815a1c5bf2d7e41c114f3d73 18-Oct-2013 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates (20XY-2012 ==> 20XY-2013)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13658 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
49984eadbda78d8edea43f7839f4651a04ca419a 18-Oct-2013 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> arm-linux only: make unwinding by stack scanning (a nasty hack)
be controllable from the command line. Fixes (kind of) #289578.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13657 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a11ec17946cdbafb336e9121b64961c0633af2e7 18-Oct-2013 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Followup to r13652 (make the translation cache size be command-line
controllable): reduce MAX_N_SECTORS to 24, speed up Sector
initialisation, wording tweaks.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13655 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8e1bee406c191820bc3b22bf55cfa69ef5fdcd8b 18-Oct-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Allow the user to dimension the translation cache
A previous commit had decreased to 6 (on android) and increased to 16
(other platforms) the nr of sectors in the translation cache.
This patch adds a command line option to let the user specify
the nr of sectors as e.g. 16 sectors might be a lot and cause
an out of memory for some workloads or might be too small for
huge executable or executables using a lot of shared libs.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13652 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
e5b6cc4166d79e1aa1ce801476d30c3af31d7fc1 02-Jul-2013 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13441 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3bcd51daf1fbfdec973b102e245dd5833e2c48a3 12-Jun-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> improve --help for --main-stacksize and supported ARM cpu
If the command line option --main-stacksize is not used,
the current ulimit value is used, with a min of 1MB
and a max of 16MB. Document this min/max default formula
in the --help.

Also indicate that Valgrind supports ARMv7


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13426 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
46207652a0c99a2c8b0f05eafce3ca3ec533c121 20-Jan-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement --merge-recursive-frames + provide VALGRIND_MONITOR_COMMAND client req.

In a big applications, some recursive algorithms have created
hundreds of thousands of stacktraces, taking a lot of memory.

Option --merge-recursive-frames=<number> tells Valgrind to
detect and merge (collapse) recursive calls when recording stack traces.
The value is changeable using the monitor command
'v.set merge-recursive-frames'.

Also, this provides a new client request: VALGRIND_MONITOR_COMMAND
allowing to execute a gdbsrv monitor command from the client
program.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13246 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
17c5e2e3a2f48970063ea43a9abee3e11c72cb04 28-Dec-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improvements to the built-in profiling infrastructure:

--profile-flags=00000000 now prints summary statistics, one line per
profiled block, but with no translation details. Previously it had
no effect.

--profile-interval=<number> is a new flag that causes the profile data
to be dumped and zeroed every <number> event checks. This makes it
possible to get profile data without waiting for runs to end, and to
get profile data which depends on the current workload etc. If
--profile-interval=0 or is unset, the profile is printed only once, at
the end of the run, as before.

--profile-flags=XXXXXXXX (for at least one nonzero X) prints the
summary lines both at the start and end of the profile, so you don't
have to scroll back up to the top to see the summary.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13213 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
c30cd9bdc3c13c79a2e0281302b115c3d220bc9d 06-Dec-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make diagnostics for SIGILL more controllable (Valgrind part).
Fixes #309425. (Mark Wielaard, mjw@redhat.com)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13164 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8b6573dd1f5b4ab512a6e70ce23eecd82733aae1 05-Dec-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a new command line flag, --extra-debuginfo-path=path, that allows
specification of an extra directory in which to look for debuginfo
objects. Fixes #310792. (Alex Chiang, achiang@canonical.com)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13154 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
06444379afbcc0543532872b0e1896c66d2cdf01 12-Oct-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Some wrong options silently ignored if starting with same letters as valid option

For example, options below are silently "accepted"+ignored:
valgrind --profile-heaps=yes --max-stackframes=35 memcheck/tests/trivialleak
valgrind --profile-heaps=oui --max-stackframes=3.141592654 memcheck/tests/trivialleak

Also fixed the on-line --help output for option --core-redzone-size



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13037 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
5b240c20b48c86955e574d5880a145927c60a686 15-Aug-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement --vex-iropt-register-updates=sp-at-mem-access

Option sp-at-mem-access can be used by tools which do not
need an up to date BP and IP at each mem access.
It is needed however to have SP up to date at each memory
access, as an up to date SP is needed to grow the stack in
m_signals.c

Tools massif, cachegrind and callgrind are using sp-at-mem-access
as default.
None tool could also use sp-at-mem-access but default is kept
to unwindregs-at-mem-access (similar to memcheck, drd, helgrind, exp-sgcheck).

exp-dhat, exp-bbv, lackey have not been looked at to see if they
could make use of sp-at-mem-access.

Validated on x86, amd64, ppc64 and s390x.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12872 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
260c6486b5484b7dfd016248706c2aa555668768 07-Aug-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a couple of useful examples to the --help text for
--soname-synonyms.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12855 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
33722a6e0450765e50505ada7f487a4b6a36bcac 05-Aug-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs following r12843.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12844 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0c0291ae749d16571a18d48f546e2b14d2ebf220 02-Aug-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove --vex-iropt-precise-memory-exns, implement --vex-iropt-register-updates

* Option --vex-iropt-precise-memory-exns has been removed.
It is replaced by --vex-iropt-register-updates which accepts
3 values : 'unwindregs-at-mem-access' (replacing
--vex-iropt-precise-memory-exns=no), 'allregs-at-mem-access'
(replacing --vex-iropt-precise-memory-exns=yes)
and a new value 'allregs-at-each-insn'.
'allregs-at-each-insn' allows the Valgrind gdbserver to always
show up to date values to GDB.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12809 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
d99c26a4bc18fd3b17c4626c9c1fbd1583388660 01-Aug-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement --redzone-size and --core-redzone-size

* For tools replacing the malloc library (e.g. Memcheck, Helgrind, ...),
the option --redzone-size=<number> allows to control 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.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12807 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9aa15b7350fc510361290d7ada6e9ddd26bf69fa 03-Jul-2012 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update exp file (should have been part of r12701).


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12703 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
1e470b5ec96bdd4fb46750d4e2e596e194af56fe 11-May-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix 219156 support static malloc or alternate malloc lib (e.g. tcmalloc) with new option --soname-synonyms

* pub_tool_redir.h : define the prefix to be used for "soname synonym"
place holder
* vg_replace_malloc.c : define synonym place holder for malloc related
functions
* m_redir.c : when detecting a soname synonym place holder redir spec, search
in clo_soname_synonyms if there is a synonym pattern.
If yes, replace the soname pattern. If not, ignore the redir spec.
* various files: implement or document the new clo --soname-synonyms
* new test memcheck/tests/static_malloc.vgtest



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12559 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
78bfc711d3e684c76eeab5f89a94a78d40ed6f4b 08-Dec-2011 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add command-line option --fair-sched=[no|yes|try]. Use --fair-sched=try
when running the annotate_hbefore regression test. Closes #270006.

To do: update manual.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12280 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
d19fd67f4c5ed468c9fcc17387de821eada0cc2a 23-Oct-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs following update of copyright dates.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12208 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
cc3de2dfcb3b724ecd305d9a30e9095fae6664c5 18-Aug-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a new simulation hint, --sim-hints=fuse-compatible, which causes
a bunch of file-related syscalls to be handled on the might-block
syscall path rather than the fast syscall path. This fixes deadlocks
when running some FUSE-specific filesystem codes. Fixes #278057.
(Mike Shal, marfey@gmail.com)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11993 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
1568e17cf07007c677274ce877973c7ed9357df2 18-Jun-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Minor GDBserver source tidying. Also a small usability fix: if
--vgdb-error=N is specified, print a bit of text telling the user the
magic commands to give GDB in order to attach to the process.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11822 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
6dbcc639e7138f80cf82f5bbcd426df0a293eb0d 07-Jun-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a fourth --smc-check= variant, --smc-check=all-non-file. This
adds self-modifying-code checks to all guest code taken from mappings
which are not file backed, but omits checks in code from file backed
mappings. This has the effect of giving complete smc-coverage of JIT
generated code -- since that is invariably generated into anonymous
mapped areas -- without burdening non-JIT generated code with such
checks. Running Firefox 6, --smc-check=all-non-file reduces by a
factor of between 3 and 10 the number of translations requiring a self
check, compared to --smc-check=all. These changes depend on the vex
interface changes in r2158.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11798 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3b290486cd4cd601b20e04340e593c9ed9717e5f 06-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement a GDB server in Valgrind. See #214909.
(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11727 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9ab64a4d3043c251561419d0e0f51492172b1072 06-Dec-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> New command line option: --trace-children-skip-by-arg, which allows
chase/nochase decisions for child processes to be made on the basis
of their argv[] entries rather than on the name of their executables.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11483 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
e089f012b564f8abef451fe7a5a135a71fb6488d 13-Oct-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Documentation update for 3.6.0 (not including NEWS).


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11440 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
14cdbf8f4ac7e49de2bced6546f7867b2e0655f0 12-Oct-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make the --prefix-to-strip=... command-line option added in r11312
behave more like the original proposal in #245535. This makes it
more flexible and general. Also rename it.

* new name is --fullpath-after=

* allow multiple instances of --fullpath-after=

* don't require the specified strings to be prefixes, only substrings

But retain the elegant backwards-compatibility trick in Bart's r11312
commit: if --fullpath-after= is not specified at all, then behave
exactly as before.

Fixes #245535. A mixture of patches from Bart Van Assche
(bart.vanassche@gmail.com), Alexander Potapenko (glider@google.com),
and me (integration and documentation).



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11430 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
5dd0190bc0ea66f8ffa7218c66f5a2e1c7b51b30 31-Aug-2010 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Added command-line option --prefix-to-strip=... Closes #245535.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11312 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b1cc5d666cc8f8065419e4a8c819ed0b8256a764 06-Jul-2010 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make error messages at start-up more consistent. Every line of such
messages now begin with "valgrind: ", and they're more often printed before
the preamble. This required introducing a new message kind, Vg_FailMsg, and
functions VG_(fmsg) and VG_(fmsg_bad_option), and removing
VG_(err_bad_option).

Where we used to have horrible output like this:

[ocean:~/grind/ws2] vg5 --tool=massif --threshold=101 date
==31877== Massif, a heap profiler
==31877== Copyright (C) 2003-2010, and GNU GPL'd, by Nicholas Nethercote
==31877== Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright info
==31877== Command: date
==31877==
==31877== --threshold must be between 0.0 and 100.0
valgrind: Bad option '--threshold'; aborting.
valgrind: Use --help for more information.

We now have nice output like this:

[ocean:~/grind/ws2] vg2 --tool=massif --threshold=101 date
valgrind: Bad option: --threshold=101
valgrind: --threshold must be between 0.0 and 100.0
valgrind: Use --help for more information or consult the user manual.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11209 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
f9ebc3956087ce01561c4ab3faf5a8983b0f7c1c 10-May-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> New flag --require-text-symbol=:sopatt:fnpatt, to be used to check
that specified shared objects contain specified symbols. Along with a
couple of regtests that unfortunately will fail on MacOSX.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11125 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9eecbbb9a9cbbd30b903c09a9e04d8efc20bda33 03-May-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates to 2010.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11121 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
f6122a06222625b8e632a19ad1a09a8f13e26afe 27-Mar-2010 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> The help text printed by command-line option -h does now show the default
value for option --read-var-info. Fixes bug #231458.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11097 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
540cc4a46fea7e3fef9703fb1c8c106b5b558fd7 15-Jan-2010 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add command line flag --vex-guest-chase-cond=no|yes [no] to control
whether front ends should speculatively chase through conditional
branches. Disabled by default.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11026 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
064212709dc8988a48d2cbde5b90528952d8cd74 05-Nov-2009 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> New flag: --trace-children-skip=patt1,patt2,etc
Specifies a comma-separated list of executable-names
(with "*" and "?" wildcards allowed) that should not be traced into
even when --trace-children=yes. Modified version of a patch
from Bill Hoffman. Fixes #148932.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10927 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0f212dc3ed1402136eb094a57cab48155e50cb54 20-Aug-2009 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fixed bug #204317: regression tests none/tests/cmdline[12] fail if
the gdb path detected by configure differs from /usr/bin/gdb.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10855 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
2d9e874b7a628ada216f09cc4f065798c65fffa4 07-Aug-2009 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Tidy up of messaging:

* For all tools and the core, don't show statistics when -v is in
effect. Instead, try to restrict -v to mostly user-useful
stuff.

* A new flag --stats=no|yes [no] produces statistics output instead.

* Fix longstanding problem in that Memcheck's leak checker ran after
the core's error manager module shut down, thereby not showing use
counts of leak suppressions. This fixes #186790.

* As a consequence, the leak checker text output of Memcheck has
changed a bit -- leak check is done before the final error
summary is done (much more logical), and the output has been
tidied up a bit.

* Helgrind, Drd and Ptrcheck now also print "For counts of
detected and suppressed errors, rerun with: -v", which makes
them consistent with Memcheck in this regard. These are
filtered out by the regtest filter scripts.

For all tools except Memcheck, the regtests are unchanged. On
Memcheck regtests still fail due to rearrangements of the leak
checker output. This will be fixed by a followup commit.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10746 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
97db761d2a94fc7a349aee9359ef85828d9618b6 04-Aug-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Various option-related tweaks:

- Match the ordering of the non-tool-specific options in the usage message
with the order in the user manual. As a result, we now always print
--alignment and --trace-malloc in the core's usage messages, which saves
malloc-replacing tools from doing it themselves (and brings it in line
with options that only apply to error-collecting tools).

- Improved the presentation of the Vex options with --help-debug.

- Removed documentation of -d in the manual because it's a debugging-only flag.

- Documented --read-var-info in the manual. This fixes bug 201169.

- Renamed --auto-run-dsymutil as --dsymutil and documented it in the usage
message.

- Fixed an XML error in manual-core-adv.xml.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10703 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
05a8917ed79c7b76ad4764087e9262c0ef8befd9 29-Jul-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Started overhauling the documentation:
- There were detailed descriptions of all the tools in the Quick Start
Guide, the Manual introduction, and the start of each tool chapter. To
avoid duplication/overlap, I removed these altogether from the Quick Start
Guide, and shortened them in the intro.

- Improved the description of what errors Memcheck can find.

- Made all tool chapters start with "Overview" section, for consistency.

- Made the "run with --tool=XXX" bit consistent in each tool chapter.

- Made all tool chapter titles match the description given when running them.

- Added BBV to the User Manual intro.

- Generally clarified, updated, and future-proofed various bits of text in
the Quick Start Guide and User Manual introduction.

Also:
- Changed Nulgrind's start-up description to "the minimal Valgrind tool".

- Fixed some punctuation in the usage message.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10652 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
e4b9921b09e54c52bba314f92a8a86d0ef71ae30 22-Jul-2009 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated expected output.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10522 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8fd875852a05e2eb3659344654faf1922a44ef9b 15-Jul-2009 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge none/ changes from branches/MESSAGING_TIDYUP r10464.
See trunk r10465 commit message for details.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10475 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
10b9aea527d9e58518791522d2d3c610ed6f295e 14-Jul-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Shorten the preamble by moving some of it into the --help output. This
partly fixes bug 197933.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10451 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9f207460d70d38c46c9e81996a3dcdf90961c6db 10-Mar-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated copyright years.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9344 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9ba91f4c4ae800d23b81c53e303a80760183580c 22-Dec-2008 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8863 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
6f089c7722d75946c7de10b4e79190aaea483118 08-Nov-2008 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8739 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b8b79addf04dd5d0b558916e26df0b1927cbd758 03-Mar-2008 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in the DATASYMS branch.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7540 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
05b48236c267bc45a1b35371c4d95417316ca79b 13-Feb-2008 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix minor breakage in 7 tests.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7405 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
95d86c091a218e904e912354efa4f952a9712e82 18-Dec-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improve handling of programs which require very large main thread
stacks. Instead of hardwiring the main thread stack to a max of 16MB
and segfaulting the app beyond that point, allow the user to specify
the main stack size using the new flag --main-stacksize=<number>.

If said flag is not present, the current default, which is "MIN(16GB,
current ulimit -s value)", is used.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7302 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
28f80e9ab821ca87d8c88d2a28dbc600b8226da0 24-Nov-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7206 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
374a36dbfb6d08ed8d77c31a88e198a861ffadf0 23-Nov-2007 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fixed up the log file mess throughout, including the docs. This killed
--log-file-qualifier and --log-file-exactly.

Updated NEWS some in preparation for 3.3.0.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7202 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8af928c04bd44cccff53e52bb3602530b74ce6a9 13-Feb-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated expected output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6590 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
9ebd6e0c607fa30301b1325874eb8de871c21cc5 08-Jan-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6488 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3477e8cca7c9ef1e35dd1503d1e31fe584884197 17-Oct-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6305 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
33dbfce5f650eadd19293175aec5d79afec0debc 03-Jun-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Clarify usage instructions for --trace-flags.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5950 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b80c828922f31a59e31e12de1c63d8ee11c3ee22 27-May-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Oops, track date change in r5940.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5941 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
365985f6538a282be58a1681b0a98bf83b5c7561 13-May-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs following r5895.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5901 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
ca54af3adebe3ff9126ea2c2f6b9a9921269f9c4 16-Apr-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove tool-specific code (which says which tools allow XML) from the core
by introducing a new "need": VG_(needs_xml_output)().


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5854 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
33afdb5127da66fc776f2cdcda8c6a0094bf21f5 17-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change the default --trace-notbelow= number from zero to infinity,
effectively, since that's a more useful default.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5539 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0ec07f32bbbb209d749b9974408e6f025ad40b31 12-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in function wrapping support from the FNWRAP branch. That
branch hereby becomes inactive. This currently breaks everything
except x86; fixes for amd64/ppc32 to follow.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5520 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
bcd75fcb80c13b9828a4c33b0d7acf1499e14135 19-Dec-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove all remaining profiling gunk.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5388 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
00cfcfc962cc3a377cdc7a6e0ec2ea9de4f26e61 12-Nov-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Don't imply that the --tool option is mandatory.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5100 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
628add6061c08b1e93562bd5559e40f6d158bbb6 12-Nov-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rename --simulation-hints as --sim-hints for brevity.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5099 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3c3f0c11a00ef5a93ca070e58cb64ac61a257cb0 08-Nov-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Document the --kernel-variant= option.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5040 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
bbe14b13426aa632726b18685eb4f1190e0dca52 04-Nov-2005 tom <tom@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix up references to log files names containing "pid" in them and
a few other related items. Patch from James Begley <james@hafro.is>.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5004 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
74b4cca0cbe20aa94daadd8afba0ba37fbd82084 20-Oct-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove all remaining references to pointercheck. It's sad to see it
go, but realistically we can't implement it portably, at least without
considerable performance overhead and some additional complexity.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4956 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
19617ae5ba420da54f286aaf1ecceafeec6b766a 20-Oct-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> The Spin-Doctor arrives in Valgrind-Land: rename --weird-hacks= to
--simulation-hints=. Bwaha.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4955 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
20b4a1567e23d84959c22269f2398e02a5462a00 20-Oct-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make the usage message a little neater and more self-consistent.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4948 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a0461a613643f6cbcb88d2e7297d19dd4c0715eb 28-Sep-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Get rid of the "ioctl-mmap" weird-hack flag.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4800 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a23e6c9a3ba38d0e6ad3396e853d5e9474f0c912 27-Sep-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix scalar and cmdline[12].



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4790 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
ce545557cb666095c20c934aa36391790ee61639 26-Jul-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Recategorise options in the usage message.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4256 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3448a1cf442425f279f6c1dbd87bb1e738507e4b 24-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Don't claim that the --single-step= and --optimise= flags exist any
more. They have been replaced by --vex-guest-max-insns= and the
--vex-iropt-* flags.




git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4241 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8637545b036ec3def92ef093009c9d9517060e39 24-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> --branchpred= doesn't do anything (I'm not sure what it ever did do). Rm'd.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4239 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
3d7c2f0b8e6d8e4a70b6aaaa6f14a29f3b88ef4c 24-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Get rid of --support-elan3=. This flag wasn't doing anything since
the Elan3 user-space driver now works on unmodified Valgrind.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4238 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
6c3a219727dead14309abf431f72ca1f99b8ca37 24-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rename --smc-support= to --smc-check=.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4237 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
483398ece74f045030f01f323e3c13cfe5e43222 20-Jul-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix broken tests.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4207 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
4daf4392cf89e2a806a1fceb5c554c380bb532b9 07-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4124 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
f178c30c78a9c60157de0e48236f31ecebfc6fd0 20-May-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix trivial regtest failures


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3777 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
272b21688397481c917c83f9943775adcf9b7f68 17-May-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update website address.

MERGE TO 2.4 REPOSITORY



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3753 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
1dd628ae33d2bb9cafd3313ee680d5dd86e44da2 03-May-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected output.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3605 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
412ad6ec7fc46fec5368adad68ca9febeb9bf10f 03-Apr-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3513 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
8f01fbe8fcff78d3131724a5fd540fbab89d38b5 20-Mar-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update expected outputs following institution of default --show-emwarns=no


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3390 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
cc6cc144e2f346e0c68efcdea09e4dcc515c62e5 12-Mar-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> --num-callers default is now 12, so say that in the help.
Fix cmdline tests for match new --num-callers stuff.

MERGED FROM CVS HEAD



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3315 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
5361242f022b38fadb4cdf02428cea8b8d901a90 12-Mar-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright notice for 2005 on all relevant files. Don't bother trying
to be selective about it.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3303 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
613812efb772d7ed7ff565aad0c33f46219b099b 11-Mar-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix Nulgrind's filter_stderr, and also fix the none/tests/cmdline2 test
(required fixing the usage msg slightly).



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3278 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b5f6f51ebcac183818061bf53427a3e7808ef10d 11-Mar-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in changes from the 2.4.0 line. This basically brings in the
overhaul of the thread support. Many things are now probably broken,
but at least with --tool=none, simple and not-so-simple threaded and
non-thread programs work.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3265 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
fa8ec113ecff891bdefb13dd361b40a503a992f8 19-Jan-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Complete rewrite (I think this is the 4th incarnation) of translation
table/cache management. Two main changes. (1) Translation areas are
recorded using VexGuestExtents, so that Vex is now properly supported
and code deletion works correctly. (2) Low overhead BB profiling,
enabled by the --profile-flags=<XXXXXXXX> option. This finds the top
N bbs at exit and shows them, so as to give a basis from which to do
performane tuning.

To support this, the way tt/tc work is changed. It is still a
sectored arrangement, but now each sector has its own hash table.
This simplifies a lot of things.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3226 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
09272c7029dc3e374e66a3534b5ac3e505e9bf3a 11-Jan-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update some expected regtest outputs.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3221 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
b67b2a2fc39f8098ea53b001570a7d88a02e77a3 06-Dec-2004 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated expected output


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3181 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
c767b4390fe6dc173f1125457f46b3e2c277b193 29-Nov-2004 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix reg test.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3142 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
7eea51f6528912dabac42bc55fd9777ebbb67af7 26-Nov-2004 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix this test.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3112 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0dbb7de509d30f5fa67f724b6b260be2202cad70 26-Nov-2004 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Second (failed) attempt to get cmdline2 to work right.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3110 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
6233a38b2ab64e85c30513b6636ad26afe4ffbec 21-Aug-2004 thughes <thughes@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add support for a --time-stamp option that causes each message output
by valgrind to include a time stamp. This fixes bug #70587.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2594 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
08fa9a789bd4747bb753fcbf53318c0de9426fc8 16-Jul-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Slightly change, with J's approval, startup copyright messages to better
reflect reality.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2489 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
0d5885069e39a966c4fb9e8b04ae475aafa300dd 21-Jun-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Streamlined --help message a bit.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2430 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
f854867c39a3697ca53e417447048d0cc3ff8a87 21-Jun-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Renamed the following options:

--logfile-fd --> --log-fd
--logfile --> --log-file
--logsocket --> --log-socket

to be consistent with each other and other options (esp. --input-fd). Also
renamed some related variables. The old names still work, for backwards
compatibility, but they're not documented.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2429 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
a76368b71cb31941d1dd11340b508f065bdfd210 16-Jun-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Reinstate -h option, which disappeared at some point.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2420 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
e2be7e68a11ef80dccb78bf7d824f4318441b634 16-Jun-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Removed documentation references to the 'ioctl-VTIME' and 'truncate-writes'
weird hacks, which no longer exist thanks to the proxy lwp stuff.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2419 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp
f4928da3dcf75e364ed0636c25ddcff856ec6ca8 15-Jun-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fixed up various command line option scenarios:
- If no tool is specified, V now gives a short message and a list of
available tools. This was meant to happen previously, but a bug prevented
it from working properly; it gave the usage message instead.

- If a bad option is given, V now gives a short message rather than the full
--help. This make V consistent with all other programs I looked at.

- Now returning 0 when you do 'valgrind --help' and 'valgrind --version'
as other programs do.

- Removed VG_(startup_logging)() and VG_(shutdown_logging)() as they were
empty and have been for a long time (always?).

- Added various tests for these scenarios. Had to change the regtest
script slightly to allow for malformed command lines.

This addresses bug (wishlist) #82999.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2418 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/cmdline2.stdout.exp