mesa: log buffer ID numbers in decimal, not hexadecimal
authorBrian Paul <brianp@vmware.com>
Mon, 23 May 2016 20:58:02 +0000 (14:58 -0600)
committerBrian Paul <brianp@vmware.com>
Tue, 24 May 2016 16:26:26 +0000 (10:26 -0600)
All the other error messages use decimal.  Let's be consistent.

Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
src/mesa/main/bufferobj.c

index 34d81aa5d689932bc263821adc4384b14ee5a9b6..33bc57409b1160dab01705403dec4b153f778dd8 100644 (file)
@@ -3967,7 +3967,7 @@ _mesa_InvalidateBufferSubData(GLuint buffer, GLintptr offset,
    bufObj = _mesa_lookup_bufferobj(ctx, buffer);
    if (!bufObj || bufObj == &DummyBufferObject) {
       _mesa_error(ctx, GL_INVALID_VALUE,
-                  "glInvalidateBufferSubData(name = 0x%x) invalid object",
+                  "glInvalidateBufferSubData(name = %u) invalid object",
                   buffer);
       return;
    }
@@ -4018,7 +4018,7 @@ _mesa_InvalidateBufferData(GLuint buffer)
    bufObj = _mesa_lookup_bufferobj(ctx, buffer);
    if (!bufObj || bufObj == &DummyBufferObject) {
       _mesa_error(ctx, GL_INVALID_VALUE,
-                  "glInvalidateBufferData(name = 0x%x) invalid object",
+                  "glInvalidateBufferData(name = %u) invalid object",
                   buffer);
       return;
    }