Do not print line number in debug messages

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>

diff --git a/tests/cram/test_ucert.t b/tests/cram/test_ucert.t
index 985740def8f23e1ed9941691420a4c1abad510fb..d4d57b243da53d1193f22688d1de94b111763226 100644 (file)
--- a/tests/cram/test_ucert.t
+++ b/tests/cram/test_ucert.t
@@ -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]

diff --git a/ucert.c b/ucert.c
index 24349c41349b0d444d98e42acfd544eae86d7974..5523b02a7eb2b977ce4c28bfd3b4c082845d6513 100644 (file)
--- a/ucert.c
+++ b/ucert.c
@@ -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)