From a8e8204b18697e8f45643abdd5b32b6c8f3659ac Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Wed, 6 Mar 2019 13:29:35 +0100 Subject: [PATCH] gallium/u_vbuf: support NULL-resources MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit It's legal for a buffer-object to have a NULL-resource, but let's just skip over it, as there's nothing to do. Signed-off-by: Erik Faye-Lund Reviewed-by: Marek Olšák --- src/gallium/auxiliary/util/u_vbuf.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/gallium/auxiliary/util/u_vbuf.c b/src/gallium/auxiliary/util/u_vbuf.c index 02a59bc0575..200bfffbd39 100644 --- a/src/gallium/auxiliary/util/u_vbuf.c +++ b/src/gallium/auxiliary/util/u_vbuf.c @@ -418,6 +418,9 @@ u_vbuf_translate_buffers(struct u_vbuf *mgr, struct translate_key *key, unsigned size = vb->stride ? num_vertices * vb->stride : sizeof(double)*4; + if (!vb->buffer.resource) + continue; + if (offset + size > vb->buffer.resource->width0) { /* Don't try to map past end of buffer. This often happens when * we're translating an attribute that's at offset > 0 from the -- 2.30.2