mirek wrote on Wed, 21 September 2022 04:52

Novo wrote on Wed, 21 September 2022 01:56

I've got a different call stack with Ide::Serialize.
Maybe it will help to locate a problem.

Thanks, fixed. (Unfortunately it was complete non-bug that could not have influenced anything real, just unitialized variable that is never used again).

I do see two problems with valgrind messages:

1) Tons of "uninitialized value" messages hide real problems.
2) Nobody will use Upp with commercial apps for a very simple reason: who knows what kind of problems can be caused by these "uninitialized values".

IMHO, Upp should be checked with all available valgrind tools and all available sanitizers. At least before release.