Re: Uninitialized memory access in zic - Mailing list pgsql-hackers

From Bryan Green
Subject Re: Uninitialized memory access in zic
Date
Msg-id CAF+pBj_SH=sXYTEA4PU_VpU-ULZez=W_XcmD21BnQ-5YcEvwqQ@mail.gmail.com
Whole thread
In response to Re: Uninitialized memory access in zic  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Uninitialized memory access in zic
Next
From: Robert Haas
Date:
Subject: Re: pg_stash_advice: dump file with overlong stash name crashes worker in a restart loop