Zach Reizner f51787b1c7 gpu_display: fix dangling NULL pointer in dwl_context_setup ... If the dwl_context_setup routine fails after creating a wayland connection succesfully (e.g. if an extension is missing), the fail label is jumped to in order to disconnect the wayland connection and deallocate the wl_display structure. That label did not set self->display to NULL after calling wl_display_disconnect, which would cause the dwl_context_destroy routine to call wl_display_disconnect again, which is a double free. This CL fixes that ommission. TEST=None BUG=None Change-Id: I5b6c2d6fadda82dff4130bd4abb0e7764c15e004 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1668528 Tested-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Zach Reizner <zachr@chromium.org>		2019-06-24 23:59:06 +00:00
..
examples	crosvm: add license blurb to all files	2019-04-24 15:51:38 -07:00
protocol	gpu_display: provides wayland based output for virtio-gpu	2018-07-09 15:48:21 -07:00
src	gpu_display: fix dangling NULL pointer in dwl_context_setup	2019-06-24 23:59:06 +00:00
build.rs	edition: Remove extern crate lines	2019-04-15 02:06:08 -07:00
Cargo.toml	edition: Update gpu_buffer, gpu_display, gpu_renderer to 2018 edition	2019-04-08 22:30:19 -07:00