https://bugs.winehq.org/show_bug.cgi?id=36560
Bug ID: 36560 Summary: valgrind shows an invalid read in d3drm/tests/d3drm.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: austinenglish@gmail.com
==26440== Invalid read of size 4 ==26440== at 0x62AC4FD: D3DRMVectorSubtract (math.c:174) ==26440== by 0x62B0E0A: load_mesh_data (meshbuilder.c:1372) ==26440== by 0x629B001: load_data (d3drm.c:1119) ==26440== by 0x629BECD: d3drm3_Load (d3drm.c:1367) ==26440== by 0x6298351: d3drm1_Load (d3drm.c:394) ==26440== by 0x4CAD3AB: test_d3drm_load (d3drm.c:1595) ==26440== by 0x4CAE2C2: func_d3drm (d3drm.c:1744) ==26440== by 0x4CB192C: run_test (test.h:584) ==26440== by 0x4CB1D1B: main (test.h:654) ==26440== Address 0x4a8f40c is 0 bytes after a block of size 12 alloc'd ==26440== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==26440== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==26440== by 0x62AF98A: load_mesh_data (meshbuilder.c:1085) ==26440== by 0x629B001: load_data (d3drm.c:1119) ==26440== by 0x629BECD: d3drm3_Load (d3drm.c:1367) ==26440== by 0x6298351: d3drm1_Load (d3drm.c:394) ==26440== by 0x4CAD3AB: test_d3drm_load (d3drm.c:1595) ==26440== by 0x4CAE2C2: func_d3drm (d3drm.c:1744) ==26440== by 0x4CB192C: run_test (test.h:584) ==26440== by 0x4CB1D1B: main (test.h:654) ==26440==
https://bugs.winehq.org/show_bug.cgi?id=36560
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |valgrind
https://bugs.winehq.org/show_bug.cgi?id=36560
Thomas Faller tfaller1@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tfaller1@gmx.de
--- Comment #1 from Thomas Faller tfaller1@gmx.de --- I can't reproduce this issue. Is this still present in your test runs?
https://bugs.winehq.org/show_bug.cgi?id=36560
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #2 from Austin English austinenglish@gmail.com --- (In reply to Thomas Faller from comment #1)
I can't reproduce this issue. Is this still present in your test runs?
Not on two machines.
https://bugs.winehq.org/show_bug.cgi?id=36560
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.54.