[Mesa-dev] [PATCH] ddebug: dump driver states and shaders for apitrace calls

[Nicolai Hähnle]

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

On 09.08.2016 00:15, Marek Olšák wrote:
> From: Marek Olšák <marek.olsak at amd.com>
>
> I think this was an oversight when the PIPE_DUMP flags were added.
> ---
>  src/gallium/drivers/ddebug/dd_draw.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/src/gallium/drivers/ddebug/dd_draw.c b/src/gallium/drivers/ddebug/dd_draw.c
> index 97325e4..4ea3129 100644
> --- a/src/gallium/drivers/ddebug/dd_draw.c
> +++ b/src/gallium/drivers/ddebug/dd_draw.c
> @@ -1084,21 +1084,24 @@ dd_after_draw(struct dd_context *dctx, struct dd_call *call)
>           dd_pipelined_process_draw(dctx, call);
>           break;
>        case DD_DUMP_ALL_CALLS:
>           if (!dscreen->no_flush)
>              pipe->flush(pipe, NULL, 0);
>           dd_write_report(dctx, call, 0, false);
>           break;
>        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);
>           }
>           break;
>        default:
>           assert(0);
>        }
>     }
>
>     ++dctx->num_draw_calls;
>