GNOME Bugzilla – Bug 763362
vaapidisplay: Fix uninitialized value error for VA attribute
Last modified: 2016-03-09 17:16:38 UTC
Fix for the below issue ==20760== Conditional jump or move depends on uninitialised value(s) ==20760== at 0x666C059: get_render_mode_VADisplayAttribRenderMode (gstvaapidisplay.c:1837) ==20760== by 0x666C059: gst_vaapi_display_get_render_mode (gstvaapidisplay.c:1912) ==20760== by 0x664B9A8: gst_vaapisink_display_changed (gstvaapisink.c:1179) ==20760== by 0x6643EE4: gst_vaapi_plugin_base_ensure_display (gstvaapipluginbase.c:347) ==20760== by 0x664A0DB: gst_vaapisink_ensure_display (gstvaapisink.c:160) ==20760== by 0x664A0DB: gst_vaapisink_set_bus (gstvaapisink.c:1628) ==20760== by 0x408BFCE: gst_element_set_bus (gstelement.c:3068) ==20760== by 0x405FC48: gst_bin_add_func (gstbin.c:1160) ==20760== by 0x4064C77: gst_bin_add (gstbin.c:1374) ==20760== by 0x4102839: priv_gst_parse_launch (grammar.y:1115) ==20760== by 0x40F8C2E: gst_parse_launch_full (gstparse.c:325) ==20760== by 0x40F8EA9: gst_parse_launchv_full (gstparse.c:262) ==20760== by 0x40F8FA2: gst_parse_launchv (gstparse.c:215) ==20760== by 0x804A6EA: main (gst-launch.c:998)
Created attachment 323472 [details] [review] Fix uninitialized values error
Comment on attachment 323472 [details] [review] Fix uninitialized values error Maybe like all other of these structs it should be memset to 0 before filling it with values and passing it to any libva API?
Created attachment 323480 [details] [review] Fix uninitialized values error initializing the whole attributes to 0 before assigning the values. Not sure if we have to the same for all other structures as well.