On Tue, Aug 16, 2022 at 09:06:20AM +0300, Alexey Kuznetsov wrote: > On Tue, Aug 16, 2022 at 9:00 AM Mike Hommey <m...@glandium.org> wrote: > > > On Tue, Aug 16, 2022 at 08:30:07AM +0300, a...@me.com wrote: > > > Package: libnss3 > > > Version: 2:3.79-1 > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > debuging valgrind pidgin with result: > > > > > > ==804198== Uninitialised value was created by a stack allocation > > > ==804198== at 0xB089DC0: ssl3_MACEncryptRecord (ssl3con.c:2104) > > > > > > line correspopnds to the ssl3_MACEncryptRecord > > > > Looking at the code, it would seem to be a false positive, but I might > > have overlooked something, but you haven't pasted the most interesting > > parts of the valgrind output... > > > > Mike > > > > This output comes exactly from valgrind. No usual stack trace. Before and > below are different issues. > > BTW pidgin crashing sometimes, and only issues I can record points to the > nss library.
Usually, "Uninitialised value was created by a stack allocation" is the reason for the error, with a stack trace, that comes above it. That's the most crucial information. Without that, we don't know what is trying to use that unitialized value.
