From 168a3b8627861fbb2786839f7e276de82f883e42 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Wed, 18 Apr 2012 08:30:30 -0600 Subject: [PATCH] pipebuffer: split up assertion The problem with assert(a && b) is you don't know which term is zero when there's a failure. --- src/gallium/auxiliary/pipebuffer/pb_bufmgr_debug.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/gallium/auxiliary/pipebuffer/pb_bufmgr_debug.c b/src/gallium/auxiliary/pipebuffer/pb_bufmgr_debug.c index 2ea63d6cc79..567303aa55e 100644 --- a/src/gallium/auxiliary/pipebuffer/pb_bufmgr_debug.c +++ b/src/gallium/auxiliary/pipebuffer/pb_bufmgr_debug.c @@ -210,7 +210,8 @@ pb_debug_buffer_check(struct pb_debug_buffer *buf) if(underflow || overflow) debug_backtrace_dump(buf->create_backtrace, PB_DEBUG_CREATE_BACKTRACE); - debug_assert(!underflow && !overflow); + debug_assert(!underflow); + debug_assert(!overflow); /* re-fill if not aborted */ if(underflow) -- 2.30.2