From c5f2943ff6f3d506a06a896ab634063bff223af0 Mon Sep 17 00:00:00 2001 From: Oswald Buddenhagen Date: Sat, 12 Apr 2014 15:28:28 +0200 Subject: [PATCH] don't crash in message expiration debug print we would try to print the uids from the non-existing srec of unpaired messages while preparing expiration. this would happen only if a) MaxMessages was configured and b) new messages appeared on the slave but we were not pushing, so it's a bit of a corner case. found by coverity. --- src/sync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/sync.c b/src/sync.c index 851b2db..cdd6c3d 100644 --- a/src/sync.c +++ b/src/sync.c @@ -1360,7 +1360,7 @@ box_loaded( int sts, void *aux ) continue; if (!(srec = tmsg->srec) || srec->uid[M] <= 0) { /* We did not push the message, so it must be kept. */ - debug( " old pair(%d,%d) unpropagated\n", srec->uid[M], srec->uid[S] ); + debug( " message %d unpropagated\n", tmsg->uid ); todel--; } else { nflags = (tmsg->flags | srec->aflags[S]) & ~srec->dflags[S];