Fix 324514 gdbserver monitor cmd output behaviour consistency + allow user
to put a "marker" msg in process log output
* v.info n_errs_found accepts optional msg, added in the output of
the monitor command.
* use VG_(printf) rather than VG_(gdb_printf) when output of command
should be redirected according to v.set gdb_output|log_output|mixed_output
* also avoid calling gdb_printf in output sink processing
to output zero bytes, as gdb_printf expects to have a null terminated
string, which is not ensured when 0 bytes have to be output.
* some minor reformatting (replace char* xxx by char *xxx).
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13532 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/NEWS b/NEWS
index d5770a5..d0ef4e2 100644
--- a/NEWS
+++ b/NEWS
@@ -42,6 +42,11 @@
- Addition of GDB server monitor command 'v.info open_fds' that gives the
list of open file descriptors and additional details.
+ - Optional message in the 'v.info n_errs_found' monitor command (e.g.
+ 'v.info n_errs_found test 1234 finished'), allowing to have
+ a comment string in the process output, separating errors of different
+ tests (or test phases).
+
- Addition of GDB server monitor command 'v.info execontext' that shows
information about the stack traces recorded by Valgrind.
This can be used to analyse one possible cause of Valgrind high
@@ -449,6 +454,10 @@
322851 0bXXX binary literal syntax is not standard
FIXED 2736
+324514 gdbserver monitor cmd output behaviour consistency + allow user
+ to put a "marker" msg in process log output
+ FIXED 13532
+
207815 Adds some of the drm ioctls to syswrap-linux.c
FIXED 13486