[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: [PATCH vkd3d] vkd3d/shader: Print more info about skipped dxbc chunks.
From:       Henri Verbeet <hverbeet () gmail ! com>
Date:       2019-11-29 8:58:08
Message-ID: CAOsNvwy39BNuMUTNr6_WBRjuMKysb5k+FjQ75izcjEZ-MfGFVQ () mail ! gmail ! com
[Download RAW message or body]

On Wed, 27 Nov 2019 at 18:48, Conor McCarthy <cmccarthy@codeweavers.com> wrote:
> +#define TAG_ICFE MAKE_TAG('I', 'C', 'F', 'E')
> +#define TAG_RDEF MAKE_TAG('R', 'D', 'E', 'F')
> +#define TAG_SFI0 MAKE_TAG('S', 'F', 'I', '0')
> +#define TAG_SPDB MAKE_TAG('S', 'P', 'D', 'B')
> +#define TAG_STAT MAKE_TAG('S', 'T', 'A', 'T')
>
Where do these come from? Should that be "IFCE"?

>          default:
> -            TRACE("Skipping chunk %#x.\n", tag);
> +            memcpy(tag_chars, &tag, sizeof(tag));
> +            tag_chars[sizeof(tag)] = 0;
> +            TRACE("Skipping chunk %s.\n", tag_chars);
>              break;
That's not safe, "tag" can contain arbitrary data.

[prev in list] [next in list] [prev in thread] [next in thread]