Mesa (master): intel: Give an explanation why we are exiting for debugging.

[Eugeni Dodonov]

Module: Mesa
Branch: master
Commit: 6862b54f4d4e88ef6ebf709ea7798093ec337e2a
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=6862b54f4d4e88ef6ebf709ea7798093ec337e2a

Author: Eugeni Dodonov <eugeni.dodonov at intel.com>
Date:   Fri Sep  2 10:29:31 2011 -0300

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 <eugeni.dodonov at intel.com>

---

 src/mesa/drivers/dri/intel/intel_batchbuffer.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

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);