Skip to content

epson2: fix up uninitialized variables

While chasing a use-after-free in a consumer of sane-backends with valgrind, I noticed a lot of warnings (from valgrind) about use of uninitialized values within the epson2 backend. This is a collection of commits with a tiny bit of explanation about each uninitialized variable. Perhaps valgrind is being overly- pessimistic (and I'm not good enough with C semantics to know if these are UB, like they would be in C++, or not).

Merge request reports