[Mesa-dev] [PATCH 00/11] Klocwork related set again

Juha-Pekka Heikkila juhapekka.heikkila at gmail.com
Thu Jun 19 05:24:17 PDT 2014

Rebased and fixed on comments again, thank you Ian earlier for commenting.

For "i965: check malloc return value in intel_resolve_map_set()" I did set 
*tail to null and was running tests but I did not see any unexpected crashes. 
>From Piglit quick set there did though raise two cases where stderr has story
about assert but otherwise everything worked. I am still looking at these

"i965: Avoid null access in intelMakeCurrent()" I was a bit iffy if its 
the same behavior which I replaced.


Juha-Pekka Heikkila (11):
  i965: check malloc return value in intel_resolve_map_set()
  i965: Avoid null access in intelMakeCurrent()
  i965: Check calloc return value in gather_statistics_results()
  i965: Handle miptree creation failure in intel_alloc_texture_storage()
  i965/fs: Check variable_storage return value in fs_visitor::visit
  glsl: check _mesa_hash_table_create return value in
  glsl: Add missing null check in push_back()
  glsl: Check calloc return value in link_intrastage_shaders()
  mesa/main: Verify calloc return value in register_surface()
  mesa/main: In register_surface() verify gl_texture_object was found
  glx: Added missing null check in GetDrawableAttribute()

 src/glsl/link_atomics.cpp                           | 13 +++++++++++--
 src/glsl/link_uniform_blocks.cpp                    |  6 ++++++
 src/glsl/linker.cpp                                 |  8 ++++++++
 src/glx/glx_pbuffer.c                               | 11 +++++++----
 src/mesa/drivers/dri/i965/brw_context.c             | 10 +++++++---
 src/mesa/drivers/dri/i965/brw_fs_visitor.cpp        |  6 ++++++
 src/mesa/drivers/dri/i965/brw_performance_monitor.c |  7 ++++++-
 src/mesa/drivers/dri/i965/intel_resolve_map.c       |  6 ++++++
 src/mesa/drivers/dri/i965/intel_tex.c               |  3 +++
 src/mesa/main/vdpau.c                               | 11 +++++++++++
 10 files changed, 71 insertions(+), 10 deletions(-)


More information about the mesa-dev mailing list