]> git.ipfire.org Git - thirdparty/valgrind.git/commit
With the recent VG_(message) change,
authorNicholas Nethercote <njn@valgrind.org>
Mon, 3 Aug 2009 01:38:56 +0000 (01:38 +0000)
committerNicholas Nethercote <njn@valgrind.org>
Mon, 3 Aug 2009 01:38:56 +0000 (01:38 +0000)
commit5dfe01a847e33bf1cfdb55c17ce8450a6320a276
treee176c4efe47cfe94f86d6ed4806915c6d1eb6928
parent1bce42d94e45733d30bce65b9b08142327cd7e7f
With the recent VG_(message) change,
VALGRIND_{PRINTF,PRINTF_BACKTRACE,INTERNAL_PRINTF} were no longer appending
newlines.  This meant that --trace-malloc=yes spewed everything onto a
single line, among other things.

Rather than adding the newline back in, I chose to offically change their
behaviour to not add the newlines, as this is more flexible (and the reason
for the underlying VG_(message) change).  I updated all the relevant places
I could find.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10694
NEWS
coregrind/m_replacemalloc/vg_replace_malloc.c
docs/xml/manual-core-adv.xml
include/valgrind.h
memcheck/mc_replace_strmem.c
none/tests/Makefile.am
none/tests/vgprintf.c
none/tests/vgprintf.stderr.exp
none/tests/vgprintf.stdout.exp [deleted file]
none/tests/vgprintf.vgtest
tests/filter_stderr_basic