krb5 commit: Correct formatting of trace log microseconds

https://github.com/krb5/krb5/commit/734bf341da54e09add9160e65ea7308072b97f13
commit 734bf341da54e09add9160e65ea7308072b97f13
Author: Greg Hudson <[email protected]>
Date:   Fri Apr 3 01:04:06 2020 -0400

    Correct formatting of trace log microseconds
    
    Always use six digits with leading 0s to format the microseconds in
    trace log timestamps; otherwise a small value appears as too large of
    a fraction of a second.
    
    ticket: 8894 (new)
    tags: pullup
    target_version: 1.18-next
    target_version: 1.17-next

 src/lib/krb5/os/trace.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/lib/krb5/os/trace.c b/src/lib/krb5/os/trace.c
index 2a03ae9..7073459 100644
--- a/src/lib/krb5/os/trace.c
+++ b/src/lib/krb5/os/trace.c
@@ -411,8 +411,8 @@ krb5int_trace(krb5_context context, const char *fmt, ...)
         goto cleanup;
     if (krb5_crypto_us_timeofday(&sec, &usec) != 0)
         goto cleanup;
-    if (asprintf(&msg, "[%d] %u.%d: %s\n", (int) getpid(), (unsigned int) sec,
-                 (int) usec, str) < 0)
+    if (asprintf(&msg, "[%d] %u.%06d: %s\n", (int)getpid(),
+                 (unsigned int)sec, (int)usec, str) < 0)
         goto cleanup;
     info.message = msg;
     context->trace_callback(context, &info, context->trace_callback_data);