Re: Uninitialized memory access in zic

So, it looks like the current upstream has removed the QT bug workaround.
It looks to me that the QT bug workaround
was unconditional but the initialization was gated on want_bloat().  I
agree the upstream seems fixed.

bg

On Fri, May 29, 2026 at 11:57 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Andres Freund <andres@anarazel.de> writes:
> > Valgrind on zic, run during the build, complains about a jump depending
> on
> > uninitialized memory.  A cursory check seems to confirm that, but I don't
> > understand the code at all:
>
> That code looks noticeably different in current upstream, so I suspect
> Eggert and crew found and fixed this already.  We should probably not
> invest brain cells in tracking it down ourselves, but rather
> prioritize updating our code to some more-recent tzcode version.
> I've been meaning to do that for awhile now, will try to boost it
> to the top of my to-do list.
>
>                         regards, tom lane
>
>
>