Open uli42 opened 6 years ago
And very similar:
==17513== Syscall param writev(vector[...]) points to uninitialised byte(s)
==17513== at 0x77E1FA0: __writev_nocancel (syscall-template.S:84)
==17513== by 0x488D54: _XSERVTransSocketWritev (Xtranssock.c:2955)
==17513== by 0x47F27A: FlushClient (io.c:1080)
==17513== by 0x47F847: WriteToClient (io.c:991)
==17513== by 0x462324: ProcGetPointerMapping (devices.c:1169)
==17513== by 0x434585: Dispatch (NXdispatch.c:482)
==17513== by 0x40EF77: main (main.c:355)
==17513== Address 0xffefff778 is on thread 1's stack
==17513== in frame #4, created by ProcGetPointerMapping (devices.c:1160)
==17513== Uninitialised value was created by a stack allocation
==17513== at 0x462270: ProcGetPointerMapping (devices.c:1160)
On running
nxagent :56
with valgrind it got this: