On Thursday, October 12, 2023 4:16:17 AM EDT Paul Floyd wrote:
> Yes, a lot of users tend to be confused in thinking that once an object
> has been initialized then it will always be initialized.
>
> We can't see when is happening between the possibly incomplete
> initialization and the actual error.
You can see the actual errors reported and the memset test line which
eliminates them here:
https://github.com/WickedSmoke/xu4/compare/valgrind?expand=1
The memset is before the actual initialization in txf_begin(), so if an
uninitialized value were assigned later then it should not be changing the
valgrind report.
The actual struct names are ListDrawState & TxfDrawState and both are plain
data of 128 bytes & 72 bytes respectively.
-Karl
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
