@@ -57,9 +57,9 @@ check that ucert is producing expected results:
---
$ ucert -D -c $TEST_INPUTS/invalid.ucert
- cert_dump(406): cannot parse cert
+ cert_dump: cannot parse cert
[1]
$ ucert-san -D -c $TEST_INPUTS/invalid.ucert
- cert_dump(406): cannot parse cert
+ cert_dump: cannot parse cert
[1]
@@ -49,10 +49,10 @@ static enum {
static bool quiet;
#ifndef UCERT_STRIP_MESSAGES
-#define DPRINTF(format, ...) \
- do { \
- if (!quiet) \
- fprintf(stderr, "%s(%d): " format, __func__, __LINE__, ## __VA_ARGS__); \
+#define DPRINTF(format, ...) \
+ do { \
+ if (!quiet) \
+ fprintf(stderr, "%s: " format, __func__, ## __VA_ARGS__); \
} while (0)
#else
#define DPRINTF(format, ...) do { } while (0)
The line number does not add any significant information, and it makes the unit tests which check for these debug messages very fragile. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> --- tests/cram/test_ucert.t | 4 ++-- ucert.c | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-)