History log of /external/valgrind/tests/vg_regtest.in
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/tests/vg_regtest.in
70172361049eb4db177e293a63d000eb6f6bbfa5 05-Sep-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Avoid warnings about deprecated unescaped curly brackets in regular
expressions. Happens with perl 5.22 and newer.
Patch by Matthias Schwarzott <zzam@gentoo.org>


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15631 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
064ed8605079aa9e44e8ec375d614cce4b4e378f 26-Aug-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Support
envB: var=value
in the .vgtest file. This is similar to "env:" except the environment
variable is set prior to invoking progB.
Adapt gdbserver_tests/nlgone_exit.vgtest to fix a problem reported
by Matthias Schwarzott <zzam@gentoo.org>


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15592 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
b3a1e4bffbdbbf38304f216af405009868f43628 21-Aug-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates, to include 2015. No functional change.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15577 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
3a89e00607b6b8f6b0c38c9a217857527d29ce2f 23-Jul-2015 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> tests/vg_regtest: Always evaluate prerequisite expressions with sh

This avoids that expressions like ! <stmnt> fail with a mysterious
error message.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15438 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
8d22844dfa3625689d53e1ed0e471329de0f4c1e 03-Apr-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add testcase for BZ 231357.
To do that a small enhancement to vg_regtest was needed:
(1) New declaration to allow specifying an environemnt variable
that is set prior to invoking valgrind.
eg: env: VAR=VAL
There can be more than one such declaration
(2) prog-asis: program_name
This is like prog: except the program name is not prefixed with
the testdir.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15064 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
69e8f1712e67bc40439e91e39dc7b0ea2ed55ece 14-Mar-2015 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add option --loop-till-fail to tests/vg_regtests
to make it easier to obtain failing trace or unfiltered output for
tests that fail from time to time


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15014 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
92882e51ca7a3393849f422fee10350d59ae81d5 07-Sep-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Go back to $test_dirs after each test run or tests dir run
Otherwise, we get an error for the 2nd dir if specifying 2 directories e.g.

perl tests/vg_regtest cachegrind/tests callgrind/tests
-- Running tests in cachegrind/tests ----------------------------------
chdir: valgrind ./chdir
clreq: valgrind -q ./clreq
dlclose: valgrind ./dlclose
notpower2: valgrind --I1=32768,8,64 --D1=24576,6,64 --LL=3145728,12,64 ./../../tests/true
wrap5: valgrind ./../../memcheck/tests/wrap5
-- Running tests in cachegrind/tests/x86 ------------------------------
fpu-28-108: valgrind ./fpu-28-108
-- Finished tests in cachegrind/tests/x86 ------------------------------
-- Finished tests in cachegrind/tests ----------------------------------
`callgrind/tests' neither a directory nor a readable test file/name



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14487 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
0a961fc3cd26c69331c1f66d94edcd08633c0030 26-Jun-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Activate --read-inline-info=yes for the outer/inner setup regtest run

as this makes the inner stacktraces easier to understand
and also it exercises the inline unwinding somewhat already,
waiting for a (possible) activation by default of --read-inline-info



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14101 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
06766bdbcfe770592c0c91353cfa9e8f4d1ee4e6 23-Jun-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update the copyright notice in files ending in '.in' because the
script change-copyright-year did not handle them.
Update the script as well.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14087 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
14ab1a33f4cf3f9ed5a15794a1adb50106f7ea3a 08-Apr-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> outer/inner setup: new perf/vg_perf options to run perf tests + support translation chaining in inner.

* perf/vg_perf:
Similarly to tests/vg_regtest, perf/vg_perf now accepts the 3
optional arguments:
--outer-valgrind
--outer-tool
--outer-args

This allows easy analysis or comparison of performance between
different Valgrind versions (e.g. using callgrind, or cachegrind/cg_diff).

* See README_DEVELOPERS for more details.

* vg_regtest modified so as to use the 'in-place' build of inner, rather
than the installed version.

* added option --smc-check=all-non-file to vg_perf and vg_regtest
outer default arguments (needed when evaluating a Valgrind which does
translation chaining).




git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12496 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
72faf10172c04674ac1e31cf4f7e57be241da7da 11-Mar-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Allows to run regression tests in an outer/inner setup.

A '3 lines how to':
perl tests/vg_regtest --outer-valgrind=../trunk_untouched/install/bin/valgrind --all
(the outer results for a test xxx is in xxx.outer.log)
To run with another tool (e.g. drd), add the argument --outer-tool=drd


Still to do/things to improve:

* Most (inner) tests are successful when running under an outer
memcheck. Need to analyse the reasons of remaining failures.

* The memcheck annotations in m_mallocfree.c can be improved:
- A superblock is marked 'undefined', it should rather be marked
'no access'.
- When a free block is splitted, the remaining free block is
not made 'no access'. Instead, it is made 'undefined'.
=> this decreases the chance to find bugs.
=> this is not very efficient (e.g. the rest of a superblock
is often marked undefined repetitively).
Similarly, the free block created by VG_(arena_memalign)
is marked 'undefined'. 'No access' would be preferrable.
- mkInuseBlock marks the new block as undefined. This is probably
not needed, as VALGRIND_MALLOCLIKE_BLOCK will do it already.
- VG_(arena_malloc) should give the requested size to
VALGRIND_MALLOCLIKE_BLOCK, not the malloc usable size,
as this decreases the chance to find buffer overrun bugs.
But giving the requested size is tricky (see comments in
the code).

* need to do memcheck annotations in m_poolalloc.c
so as to allow leak checking for pool allocated elements.

* vg_regtest.in
- should analyse the results of the outer and should
produce a separate result for the tests for which
the outer detects an error or a memory leak or ...


Changes done:
README_DEVELOPERS: document the new outer/inner features.
manual-core.xml: document the new sim-hint no-inner-prefix
tests/outer_inner.supp: new file, containing the suppressions for inner.
vg_regtest.in: implement new args --outer-valgrind, --outer-tool, --outer-args.
m_mallocfree.c: annotations for memcheck.
m_libcprint.c: handle the new sim-hint no-inner-prefix
m_main.c: do an (early) parse of --sim-hints




git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12441 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
4b5c3f074cf9f275990dd6a61fbcfbe962877d98 03-Oct-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Also parse stdoutB_filter_args and stderrB_filter_args.
Forgot to do that in r12045.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12085 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
31014dae410799bfb128af2d396ee70374fa4b75 26-Sep-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change the backtrace filtering machinery for the helgrind regression
bucket. Instead of removing what we don't want to see in a backtrace
(e.g. path segments through libc and libpthread), we simply keep what
we do want to see. That way .exp files can be generic.
We need to make sure that GCC inlining does not get in the way. So all
the ..._WRK function in hg_intercepts.c are attributed as noinline.
The backtrace filtering is done in the new filter_helgrind script.
filter_stderr is simplified quite a bit.
Fixes bug #281468. See also the comments #5 and #6 there.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12045 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
eefeeb7a60a347bc851605fadd52672cbd927201 10-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improvements for testing and compilation breakage for the GDB server
on various platforms:

* In all gdbserver_tests using gdb:
Made a more general way to remove the initial start message.

* tests using threads burning cpu modified to have only 1 thread.
This makes them independent of the scheduler fairness.

* filter_gdb and filter_vgdb enhanced to anonymise
some debian 6.0/ppc specific things
some s390x/gdb 7.0, gdb 7.1 specific things

* vgdb.c: added an #include <linux/ptrace.h> to fix compilation
on s390x fedora and suse. (Christian Boerntrager)

* fixed a bug in valgrind-low.c debug log :
when a register size is 0, its image cannot be output (and register
should not be transferred).

* added a parameter --keep-unfiltered to vg_regtest.in
This will make it easier to update filter_gdb:
in case gdbserver_tests are failing due to "artificial"
differences to be filtered, re-run the tests using:
perl tests/vg_regtest --keep-unfiltered gdbserver_tests
Then a tar file with all the *.out in gdbserver_tests
will allow me to better/faster update the filter_gdb.

* made a better detection of a working PTRACE_GETREGS at compile time
and/or at run-time.

This is the patch on bug 214909 comment 69.
(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11740 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
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/tests/vg_regtest.in
ef3862559ff73146bc2020d65918cabc243b6da8 31-Aug-2010 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> Expand ${PWD} in the vgopts: line of .vgtest files.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11311 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
f6b0076ba64f5c22f9e09be70c351a9d4b095883 17-Apr-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r9103 and r9105 (add --ignore-fn to Massif) from the Darwin branch.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9567 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
61485ab2fb3be07029d03088a5d66eb804e0f535 04-Mar-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> tests/arch_test is currently being used for two purposes:
- by vg_regtest for determining if a directory name matches an architecture;
- by various .vgtest files for detecting x86/AMD64 features.

This commit splits it in two for the two different purposes, which makes
things clearer.

Specific changes

- Moved the x86/AMD64 feature detection stuff out of arch_test.c, and
into the new x86_amd64_feature.c. Updated the relevant .vgtest files for
the change.

- In vg_regtest, now a prereq command must return 0 (prereq satisfied) or 1
(prereq not satisfied). Anything else makes vg_regtest abort. This
makes obvious any problems with prereq tests rather than just making the
tests skip innocuously. (We previously had exactly such a problem on the
DARWIN branch; the x86 feature detection tests caused segfaults so the
tests were incorrectly skipped. This change will catch any similar future
problem.)

- Changed os_test from a script to a C program, matching cpu_test.

- Removed some unintentional darwin stuff from platform_test.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9316 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
0d2e58f427658a7322ca5a6a715bd33e8a2930b8 25-Feb-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Use 'diff -u' for regtests if it's supported, its output it much easier to
read than plain 'diff'.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9263 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
107bc570086d154e2be46cf044a8b0f72fb07949 16-Feb-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r9175 (don't run inappropriate OS- and platform-specific tests) from
the DARWIN branch.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9176 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
e8ffe52448e268273f7f566a98b038eb87490350 02-Mar-2008 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Ignore Emacs temporary files. Also, produce the correct .diff filename when
the .exp filename has a non-numeric suffix.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7538 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
1ee25f0cbf81a034d8189bff8bf7f1ad6be99cf0 27-Feb-2008 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make comments reflect the code.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7494 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
a8162b21279cf61a262fe6cabd9e437811b1abae 30-Nov-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Marginally enhance help message.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7258 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
79e88da1b0ca82e02ca66e9109c63da995fcc65a 10-Nov-2007 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge (from branches/THRCHECK) r7043:

Allow a test to have any number of .stderr.exp* files, so long as at
least one is found. In fact the comments in the code that claimed
that .stderr.exp[0-9] are the only ones allowed were misleading;
.stderr.exp* has always been allowed. The only functional change here
is to mandate that at least one such file exists; prior to the change
the script mandated that at least a .stderr.exp (with no other suffix)
file existed.

Purpose is to allow collections of .stderr.exp files with suffixes
arranged in some meaningful way, eg, foo.stderr.exp-glibc25-amd64.
This might help in making testsuites more maintainable when there
have to be multiple .stderr.exp files. Naming them merely as
.stderr.exp1, .stderr.exp2, etc, makes it impossible to remember
what the differences between the files actually is.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7127 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
734b805cb3af82ddd7d3ba22a0e22aba29b78305 01-Nov-2007 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merged the MASSIF2 branch to the trunk. Main changes:

- ms_main.c: completely overhauled.

- massif/tests/*: lots of them now.

- massif/perf/: added.

- massif/hp2ps: removed. No longer used.

- vg_regtest: renamed the previously unused "posttest" notion to "post".
Using it for checking ms_print's output.

Although the code has changed dramatically, as has the form of the tool's
output, the information presented in the output is basically the same,
although it's now (hopefully) much more useful. So the tool name is
unchanged.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7069 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
7358d5279a943b065f90ad02b56e39402128338b 26-Nov-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update a comment.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6373 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
3ed896035e9e6d7ac33f7cc23f95c54ef7d477ff 23-Oct-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add --valgrind-lib, to complement --valgrind, to the regtests script
(from Dave Nomura).



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6338 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
2659b16a28ca23f12f60fafe419d984becb8eaa0 17-Oct-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Don't use -C0 for diff; apparently this is a GNU-ism.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6300 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
9136899ca8bdb68de5555469d280e3f769a3418b 26-May-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Read extra args for all tests from $EXTRA_REGTEST_OPTS, which is
useful (eg) for running tests with --sanity-level= set. Print a
big warning before and after the tests if it is set.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5931 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
0001fc3062186352db6f31829b0b62953dda138e 03-Apr-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add an optional post-test check. Based on a patch from Josef W.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5817 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
1d0825ff46d57f0ce83c3fa88538a42f67022eee 27-Mar-2006 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in the COMPVBITS branch to the trunk. This is a big change to
Memcheck, replacing the 9-bits-per-byte shadow memory representation to a
2-bits-per-byte representation (with possibly a little more on the side) by
taking advantage of the fact that extremely few memory bytes are partially
defined.

For the SPEC2k benchmarks with "test" inputs, this speeds up Memcheck by a
(geometric mean) factor of 1.20, and reduces the size of shadow memory by a
(geometric mean) factor of 4.26.

At the same time, Addrcheck is removed. It hadn't worked for quite some
time, and with these improvements in Memcheck its raisons-d'etre have
shrivelled so much that it's not worth the effort to keep around. Hooray!

Nb: this code hasn't been tested on PPC. If things go wrong, look first in
the fast stack-handling functions (eg. mc_new_mem_stack_160,
MC_(helperc_MAKE_STACK_UNINIT)).


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5791 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
932d5ed2053e80768149a0baa220a51c60889e03 09-Dec-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove dead line.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5322 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
52783ca9c51977276ef0a8367bad550f283b461a 08-Dec-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fail gracefully if 'make check' hasn't been run.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5317 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
efc94adb4069659c39c88b314cdd6c0b7d06a8ae 12-Nov-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make regtests work with --enable-inner.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5098 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
45f4e7c91119c7d01a59f5e827c67841632c9314 27-Sep-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> This commit merges in changes from branches/ASPACEM (specifically,
changes from r4341 through r4787 inclusive). That branch is now dead.
Please do not commit anything else to it.

For the most part the merge was not troublesome. The main areas of
uncertainty are:

- build system: I had to import by hand Makefile.core-AM_CPPFLAGS.am
and include it in a couple of places. Building etc seems to still
work, but I haven't tried building the documentation.

- syscall wrappers: Following analysis by Greg & Nick, a whole lot of
stuff was moved from -generic to -linux after the branch was created.
I think that is satisfactorily glued back together now.

- Regtests: although this appears to work, no .out files appear, which
is strange, and makes it hard to diagnose regtest failures. In
particular memcheck/tests/x86/scalar.stderr.exp remains in a
conflicted state.

- amd64 is broken (slightly), and ppc32 will be unbuildable. I'll
attend to the former shortly.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4789 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
786603101a15b26852544e8206f29170bdb50e65 29-Jun-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix vg_regtests so it can properly handle alternative output filenames with
more than one numeric char at the end (eg. xml1.stderr.exp64).


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4050 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
2bc10126a94b421a490b2759dc50ab67ec4ee116 08-May-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> A crucial, crucial change: update my email address.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3632 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
6a32942757725bfbf39b43a5c133b439d143e790 12-Mar-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Default to using --leak-check=summary.

MERGED FROM CVS HEAD



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3312 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
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/tests/vg_regtest.in
b9c427c63a278cc612ae0ec573be7bb1abaa447f 01-Dec-2004 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Changed message at the top of files, and the startup message, and the
string in valgrind.pc.in, so that they describe Valgrind as a "dynamic
binary instrumentation framework", and don't mention platforms at all.

I had to tweak the regtest filters a bit for this.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3178 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
362c0d257b76d1f731a38f9eeb81351d9519963b 18-Nov-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Arch-abstraction:
- Added a hacky mechanism which prevents the regtest script from entering
directories for other architectures. (Eg. when running on x86/, it won't enter
a ppc/ subdir.)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3045 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
c5e1d806c4f11f91401be4b9f70ac08b1c9d6f61 18-Nov-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Generalised the reg test script again: replaced the "cpu_test" line,
which caused the test to be skipped if the CPU type wasn't appropriate,
with a "prereq" line, which specifies a command that must succeed before
the test is run.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3041 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
64bc5af199f2b6a12e87d044ed7f9c1244860ad0 18-Nov-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Generalised reg test script: instead of having a "delete:" line, for removing
files once a test has completed, we have a "cleanup:" line, which specifies a
cleanup command.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3039 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
781bed4df9b5d4e523b3b2f111e4a1d5f79534e5 19-Oct-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Arch-abstraction:
- Change regtest script to print a message if a test is skipped due to the cpu
being of the wrong type.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2803 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
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/tests/vg_regtest.in
c1f8ad91417317d6465a8326b77831a485939c52 17-Apr-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a "delete:" line to the regression test .vgtest files, to clean up any file
created by the test. Added appropriate lines to the Cachegrind and Massif
tests. Should prevent large numbers of files clogging up directories.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2372 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
ab4221970f8a69c7918cc1dc85f3ae670c11f135 01-Mar-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make vg_regtest return 1 if any tests fail. Useful for scripts that call it.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2283 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
4592db65c3ff3fd299613306dcd83b7b584a7a84 29-Feb-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Allow multiple .exp files, eg. foo.stderr.exp, foo.stderr.exp2; test will pass
as long as one matches.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2275 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
b1affa88ef798064014f9657fa6bb4a8501fdbf8 19-Jan-2004 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Patch from Tom Hughes, for bug 72643:

Patch to improve SSE/SS2 support

This patch should implement most of the missing SSE/SSE2 opcodes. About
the only ones it doesn't do are the MASKMOVxxx ones as they are quite
horrible and involved an implicit reference to EDI so I need to think
about them a bit more.

The patch also includes a set of tests for the MMX/SSE/SSE2 opcodes to
validate that they have the same effect under valgrind as they do when
run normally. In one or two cases this wasn't actually the case even
for some of the implemented opcodes, so I fixed those as well ;-)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2202 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
98abfc7bb7798c4ac4580f7e0bc7171de94a0255 16-Dec-2003 fitzhardinge <fitzhardinge@a5019735-40e9-0310-863c-91ae7b9d1cf9> This jumbo-checkin is the Full Virtualization checkin. This eliminates
Valgrind's dependency on the dynamic linker for getting started, and
instead takes things into its own hands.

This checkin doesn't add much in the way of new functionality, but it
is the basis for all future work on Valgrind. It allows us much more
flexibility in implementation, and well as increasing the reliability
of Valgrind by protecting it more from its clients.

This patch requires some changes to tools to update them to the changes
in the tool API, but they are straightforward. See the posting "Heads
up: Full Virtualization" on valgrind-developers for a more complete
description of this change and its effects on you.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2118 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
92f0b80fbc7dcdec2bb9f97c9c5cf7e35c48ad6e 19-Nov-2003 mueller <mueller@a5019735-40e9-0310-863c-91ae7b9d1cf9> only say something if there is something to say


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2037 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
137bc55f216bc7d9528f159a78cdf9025e0b02ff 14-Nov-2003 nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Started to rescind the name "skin", replacing it with "tool". Did this in all
the places that normal users will see:

- command line: --tool=foo (although --skin=foo still works)
- docs: removed all traces (included renaming coregrind_skins.html to
coregrind_tools.html)
- in the usage messages
- in error messages

Also did in in some places that I judged were unlikely to cause clashes with
existing workspaces:

- in the header comments of many files (eg. "This file is part of Memcheck, a
Valgrind tool for...")
- in the regtests script
- in the .supp files
- in AUTHORS
- in README_MISSING_SYSCALL_OR_IOCTL

Also update the AUTHORS file to mention Jeremy.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2027 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
855d93d2e9940890b28874520fa4c1677bf825e2 14-Oct-2003 jsgf <jsgf@a5019735-40e9-0310-863c-91ae7b9d1cf9> A complete reworking of Valgrind's handling of system calls and signals,
with the aim of making it more robust, more correct and perhaps faster.

This patch removes the need to poll blocking syscalls, by adding a proxy
LWP for each application thread. This LWP is a kernel thread whose job
is to run all (potentially) blocking syscalls, and also to handle signals.

This allows the kernel to do more of the work of dealing with signals,
so on kernels which do this properly (2.6), Valgrind's behavious is a
lot more posix compliant. On base 2.4 kernels, we emulate some of the
missing 2.6 functionality.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1918 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
42e23f2b5f06b8aaf68702bffa9006831877e872 05-May-2003 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> This commit allows Valgrind to be run in-place from the source tree, without
requiring "make install". This is good for two reasons:

1. shorter compile times ("make" instead of "make install")
2. don't need to install before running the regression tests

Changes:
- root Makefile now builds a libpthread.so.0 symlink to libpthread.so, which
was needed.

- startup script accepts a --in-place=<dir> option for running a non-installed
version, where <dir> is the root of the src tree

- VG_(mash_LD_PRELOAD_and_LD_LIBRARY_PATH) had to be fiddled with a bit

- tests/vg_regtest now uses the --in-place option to test the non-installed
version


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1614 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
71fe3e69d0f860cffc97acb96cb4553c6429d867 23-Apr-2003 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Changed things so that the regression test script (vg_regtest) is no longer
installed, as it was silly since the reg tests themselves aren't installed.
Updated the "make regtest" target to use the uninstalled version in tests/.

Also, vg_regtest now no longer uses the installed version of Valgrind to do the
testing, but instead coregrind/valgrind. This means that you don't have to do
make install with your buggy changes before running the regtests on them :)

I even updated the RPM package .spec file!

Thanks to Dirk M�ller for the suggestion.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1551 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
9fb16f52511969a48a056b8e71af852b0ff0da6d 23-Apr-2003 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Now counting tests and stdout failures and stderr failures separately and
correctly.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1547 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
bb936987ffdbca90f57d80c56cf10e0512e83c86 23-Apr-2003 daywalker <daywalker@a5019735-40e9-0310-863c-91ae7b9d1cf9> - fix regression tests counting
- unset $VALGRIND_OPTS (fixes 6 testsuite failures)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1545 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
0e1b514ab8e837f75a207a037ea53a6a721e9d28 15-Apr-2003 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated copyright notices for 2003. Only 4 months late.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1526 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
d8ced86d011bbc4069433f08096a5ad854d1a6e4 08-Apr-2003 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Removed support for the 1.0.X series from the regression test suite -- this
was present from before the core/skin split, which is now dead. Means the
script is slightly simpler, and we can dispense with lots of expected
foo.stderr.hd files.

Also undid accidental change to required Automake version in main Makefile.am
from my last commit, whoops.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1518 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
2f68595ed11429b7eed8a07871a2d5842e1ed5f4 22-Dec-2002 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Don't assume Perl lives in /usr/bin; do a proper test for it.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1389 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
bf89f31771289a1d4ebbb1bee3ca9723df39c458 30-Oct-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fixed minor problem in regtest script.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1271 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
584eaacf6c0cc2820a54da7323d2b01c1796cd1c 04-Oct-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> wibbles


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1184 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
db3c469408a7439182e354b6914e8558023ca59e 04-Oct-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Prettified output somewhat, so that full directory names (relative to .) are
printed, and so that directories containing no test files get a different, more
concise, message.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1176 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
c953984b8ee34ac55830b9871138b409d9d9476c 02-Oct-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Updated file descriptions in the copyright notices to reflect the core/skin
split. Each skin now has its own two-line description.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1166 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
4ba5a79d946b22c52856d62dca7c927cb306dfa3 30-Sep-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Converted all functions visible from vg_skin.h with names in CamelCaps to
use_under_scores instead, to be consistent.

Also added some missing 'extern's on function declarations in vg_skin.h.

Also added a quick note in vg_regtest.in on the simplest way to run regression
tests.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1135 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in
c2e7f483a74e57544febba85b603127c6d22c455 27-Sep-2002 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Moved vg_regtest to vg_regtest.in, using autoconf so vg_regtest now knows where
the `valgrind' script is kept, so people who install valgrind in a directory
other than the one I do don't need to use the --valgrind option all the time.

As a consequence, vg_regtests is now installed in and run out of bin/, rather
than tests/.

Also added a GPL copyright notice to vg_regtests.in.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1118 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/tests/vg_regtest.in