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 <[email protected]>

1 files changed, 4 insertions, 1 deletions

diff --git a/src/gallium/drivers/ddebug/dd_draw.c b/src/gallium/drivers/ddebug/dd_draw.c
index c1bfdaf6865..e2005edc872 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);
          }