Tighten up nonreentrant syntax-check.

We can slightly tighten up the regex's used to detect the use of
nonreentrant functions.  We can also check src/util/virterror.c
by modifying a comment; I think it's worth it to get the additional
coverage.

Signed-off-by: Chris Lalancette <clalance@redhat.com>
This commit is contained in:
Chris Lalancette 2009-10-23 12:07:17 +02:00
parent b2af10cd49
commit 03b5dc14de
2 changed files with 5 additions and 5 deletions

View File

@ -1,10 +1,10 @@
^gnulib/ ^gnulib/
^po/ ^po/
ChangeLog ^ChangeLog$
^ChangeLog-old$
^Makefile* ^Makefile*
^docs/ ^docs/
^tests/ ^tests/
^tools/virsh\.c ^tools/virsh\.c$
^tools/console\.c ^tools/console\.c$
^src/util/virterror\.c
^build-aux/ ^build-aux/

View File

@ -1157,7 +1157,7 @@ const char *virStrerror(int theerrno, char *errBuf, size_t errBufLen)
return errBuf; return errBuf;
# endif # endif
#else #else
/* Mingw lacks strerror_r() and its strerror() is definitely not /* Mingw lacks strerror_r and its strerror is definitely not
* threadsafe, so safest option is to just print the raw errno * threadsafe, so safest option is to just print the raw errno
* value - we can at least reliably & safely look it up in the * value - we can at least reliably & safely look it up in the
* header files for debug purposes * header files for debug purposes