From 6862b54f4d4e88ef6ebf709ea7798093ec337e2a Mon Sep 17 00:00:00 2001 From: Eugeni Dodonov Date: Fri, 2 Sep 2011 10:29:31 -0300 Subject: [PATCH] intel: Give an explanation why we are exiting for debugging. This could happen in 3 different cases, and ERRNO can explain what happened. First case would be EIO (gpu hang), second EINVAL (something is wrong inside the batch), and we also discovered that sometimes it happens with ENOSPACE. All of those cases are different it it could be worth to at least know what happened. Signed-off-by: Eugeni Dodonov --- src/mesa/drivers/dri/intel/intel_batchbuffer.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/mesa/drivers/dri/intel/intel_batchbuffer.c b/src/mesa/drivers/dri/intel/intel_batchbuffer.c index 21dd27c..c4bb836 100644 --- a/src/mesa/drivers/dri/intel/intel_batchbuffer.c +++ b/src/mesa/drivers/dri/intel/intel_batchbuffer.c @@ -138,6 +138,7 @@ do_flush_locked(struct intel_context *intel) } if (ret != 0) { + fprintf(stderr, "intel_do_flush_locked failed: %s\n", strerr(ret)); exit(1); } intel->vtbl.new_batch(intel); -- 2.7.4