[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SCM] GNU libidn branch, master, updated. libidn-1-24-18-g56eacb2

From: Simon Josefsson
Subject: [SCM] GNU libidn branch, master, updated. libidn-1-24-18-g56eacb2
Date: Tue, 22 May 2012 17:25:55 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU libidn".

The branch, master has been updated
       via  56eacb2d1e0575b2638200903609d68058dce727 (commit)
      from  cf725246a5585d56ccb14c46bfe2a163342ff21f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 56eacb2d1e0575b2638200903609d68058dce727
Author: Simon Josefsson <address@hidden>
Date:   Wed May 16 00:52:54 2012 +0200

    Fix valgrind wording.


Summary of changes:
 HACKING |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/HACKING b/HACKING
index b039e56..45fe63f 100644
@@ -54,10 +54,11 @@ $ make
 $ make check
 When building from version controlled sources, some developer specific
-flags are automatically enabled.  Due to compiler optimizations, you
-may run into valgrind false positives.  We ship a Valgrind suppression
-file in tests/libidn.supp and you can use it by putting the following
-in your ~/.valgrindrc:
+flags are automatically enabled.  For example, the self-checks are run
+under valgrind if available.  For various reasons, you may run into
+valgrind false positives that will cause self-checks to fail.  We ship
+a Valgrind suppression file to address common issues.  You can use it
+by putting the following in your ~/.valgrindrc:

GNU libidn

reply via email to

[Prev in Thread] Current Thread [Next in Thread]