[Mesa-dev] [PATCH 2/2] mesa: log buffer ID numbers in decimal, not hexidecimal

Brian Paul brianp at vmware.com
Mon May 23 21:01:58 UTC 2016


Err, "hexadecimal".  Will fixe before pushing.

On 05/23/2016 03:00 PM, Brian Paul wrote:
> All the other error messages use decimal.  Let's be consistent.
> ---
>   src/mesa/main/bufferobj.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/mesa/main/bufferobj.c b/src/mesa/main/bufferobj.c
> index 34d81aa..33bc574 100644
> --- a/src/mesa/main/bufferobj.c
> +++ b/src/mesa/main/bufferobj.c
> @@ -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;
>      }
>



More information about the mesa-dev mailing list