https://bugs.kde.org/show_bug.cgi?id=253657
--- Comment #21 from Austin English <austinengl...@gmail.com> --- (In reply to Daniel Lehman from comment #20) > Created attachment 118764 [details] > leakage.exe and pdb > > attached tested with: > - Visual Studio 2017 (15.9.8) > - wine 4.3 > - valgrind-3.15.0.GIT (4816357b5c7ee5284cdf72800a81d2dd1845388f) Thanks. I wasn't able to reproduce, with same valgrind git commit (+ your patches) and wine-4.0-rc1 (last wow64 build I have handy, but given that you used 3.15 before I don't think it matters). What VALGRIND_OPTS are you using? I tried with: austin@laptop:~$ export VALGRIND_OPTS="-q --trace-children=yes --track-origins=yes --leak-check=full --num-callers=20 --vex-iropt-register-updates=allregs-at-mem-access" and got: austin@laptop:~$ ~/src/valgrind/vg-in-place /opt/oldwow64/wine-4.0-rc1/bin/wine leakage.exe ; echo $? preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 preloader: Warning: failed to reserve range 0000000000110000-0000000068000000 ==6365== Conditional jump or move depends on uninitialised value(s) ==6365== at 0x14005F7DE: ??? ==6365== by 0x51B686B7C272: ??? ==6365== Uninitialised value was created by a stack allocation ==6365== at 0x14004BB17: ??? ==6365== 00007FFFFE01B5F0 setframe: 00007FFFFE20FCD0 00007FFFFE01F7A0 ==6365== 12,345 bytes in 1 blocks are definitely lost in loss record 86 of 88 ==6365== at 0x7BC5B385: initialize_block (heap.c:238) ==6365== by 0x7BC5B385: RtlAllocateHeap (???:0) ==6365== by 0x140006BDA: ??? ==6365== ==6365== 23,456 bytes in 1 blocks are definitely lost in loss record 88 of 88 ==6365== at 0x7BC5B385: initialize_block (heap.c:238) ==6365== by 0x7BC5B385: RtlAllocateHeap (???:0) ==6365== by 0x140006C8C: ??? ==6365== by 0x51B686B7CD62: ??? ==6365== 0 did I miss a step? -- You are receiving this mail because: You are watching all bug changes.
