Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm

Em qui., 20 de jun. de 2024 às 08:54, Tomas Vondra < tomas.von...@enterprisedb.com> escreveu: > > > On 6/20/24 13:32, Ranier Vilela wrote: > > Em qui., 20 de jun. de 2024 às 07:28, Tomas Vondra < > > tomas.von...@enterprisedb.com> escreveu: > > > >> Hi, > >> > >> While running valgrind on 32-bit

Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm

On 6/20/24 13:32, Ranier Vilela wrote: > Em qui., 20 de jun. de 2024 às 07:28, Tomas Vondra < > tomas.von...@enterprisedb.com> escreveu: > >> Hi, >> >> While running valgrind on 32-bit ARM (rpi5 with debian), I got this >> really strange report: >> >> >> ==25520== Use of uninitialised value of

Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm

Em qui., 20 de jun. de 2024 às 07:28, Tomas Vondra < tomas.von...@enterprisedb.com> escreveu: > Hi, > > While running valgrind on 32-bit ARM (rpi5 with debian), I got this > really strange report: > > > ==25520== Use of uninitialised value of size 4 > ==25520==at 0x94A550: wrapper_handler

confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm

Hi, While running valgrind on 32-bit ARM (rpi5 with debian), I got this really strange report: ==25520== Use of uninitialised value of size 4 ==25520==at 0x94A550: wrapper_handler (pqsignal.c:108) ==25520==by 0x4D7826F: ??? (sigrestorer.S:64) ==25520== Uninitialised value was created