From: Marek Olšák <marek.olsak@amd.com>
Date: Sun, 7 Aug 2016 14:24:40 +0000 (+0200)
Subject: ddebug: dump driver states and shaders for apitrace calls
X-Git-Tag: upstream/17.1.0~7492
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=06b2fd04f6bc2f511f0c67a9b18f01b8f7296edc;p=platform%2Fupstream%2Fmesa.git

ddebug: dump driver states and shaders for apitrace calls

I think this was an oversight when the PIPE_DUMP flags were added.

Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
---

diff --git a/src/gallium/drivers/ddebug/dd_draw.c b/src/gallium/drivers/ddebug/dd_draw.c
index c1bfdaf..e2005ed 100644
--- a/src/gallium/drivers/ddebug/dd_draw.c
+++ b/src/gallium/drivers/ddebug/dd_draw.c
@@ -1091,7 +1091,10 @@ dd_after_draw(struct dd_context *dctx, struct dd_call *call)
       case DD_DUMP_APITRACE_CALL:
          if (dscreen->apitrace_dump_call ==
              dctx->draw_state.apitrace_call_number) {
-            dd_write_report(dctx, call, 0, false);
+            dd_write_report(dctx, call,
+                            PIPE_DUMP_CURRENT_STATES |
+                            PIPE_DUMP_CURRENT_SHADERS,
+                            false);
             /* No need to continue. */
             exit(0);
          }