[Bug 36189] New: valgrind shows an invalid write in comctl32/tests/listview.c

https://bugs.winehq.org/show_bug.cgi?id=36189

Bug ID: 36189
           Summary: valgrind shows an invalid write in
                    comctl32/tests/listview.c
           Product: Wine
           Version: 1.7.17
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: comctl32
          Assignee: [e-mail]
          Reporter: [e-mail]

==7218== Invalid write of size 4
==7218==    at 0x53B6117: EDIT_WM_KillFocus (edit.c:3566)
==7218==    by 0x53BB19C: EditWndProc_common (edit.c:5052)
==7218==    by 0x542BF12: EditWndProcA (winproc.c:1077)
==7218==    by 0x542943D: ??? (winproc.c:173)
==7218==    by 0x54295B2: call_window_proc (winproc.c:244)
==7218==    by 0x542B8CB: CallWindowProcA (winproc.c:955)
==7218==    by 0x5184C7A: CallWindowProcT (listview.c:1560)
==7218==    by 0x518ECEA: EditLblWndProcT (listview.c:5900)
==7218==    by 0x518EDA5: EditLblWndProcA (listview.c:5942)
==7218==    by 0x542943D: ??? (winproc.c:173)
==7218==    by 0x54295B2: call_window_proc (winproc.c:244)
==7218==    by 0x542B8CB: CallWindowProcA (winproc.c:955)
==7218==    by 0x4E89662: editbox_subclass_proc (listview.c:729)
==7218==    by 0x542943D: ??? (winproc.c:173)
==7218==    by 0x54295B2: call_window_proc (winproc.c:244)
==7218==    by 0x542B5DF: WINPROC_CallProcWtoA (winproc.c:858)
==7218==    by 0x542B78A: WINPROC_call_window (winproc.c:902)
==7218==    by 0x53E80F8: call_window_proc (message.c:2223)
==7218==    by 0x53EAF96: send_message (message.c:3260)
==7218==    by 0x53EB5B4: SendMessageW (message.c:3454)
==7218==  Address 0x4a71ab4 is 12 bytes inside a block of size 114 free'd
==7218==    at 0x7BC4C704: notify_free (heap.c:263)
==7218==    by 0x7BC51049: RtlFreeHeap (heap.c:1762)
==7218==    by 0x7BC75950: RtlFreeUnicodeString (rtlstr.c:319)
==7218==    by 0x7BC667FF: RtlSetCurrentDirectory_U (path.c:1016)
==7218==    by 0x7B8638D9: init_current_directory (process.c:906)
==7218==    by 0x7B8645E0: __wine_kernel_init (process.c:1179)
==7218==    by 0x7BC5AC35: __wine_process_init (loader.c:3103)
==7218==    by 0x403C7FF: wine_init (loader.c:952)
==7218==    by 0x7BF01192: main (main.c:237)
==7218==

[Bug 36189] valgrind shows an invalid write in comctl32/tests/listview.c

https://bugs.winehq.org/show_bug.cgi?id=36189

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |valgrind

[Bug 36189] valgrind shows an invalid write in comctl32/tests/listview.c

http://bugs.winehq.org/show_bug.cgi?id=36189

Sebastian Lackner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Sebastian Lackner  ---
This problem could be the same one as in
http://bugs.winehq.org/show_bug.cgi?id=36188 - does the same patch also help
here?

[Bug 36189] valgrind shows an invalid write in comctl32/tests/listview.c

https://bugs.winehq.org/show_bug.cgi?id=36189

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Austin English  ---
(In reply to Sebastian Lackner from comment #1)
> This problem could be the same one as in
> http://bugs.winehq.org/show_bug.cgi?id=36188 - does the same patch also help
> here?

Yep. Marking as a dupe.

*** This bug has been marked as a duplicate of bug 36188 ***

[Bug 36189] valgrind shows an invalid write in comctl32/tests/listview.c

https://bugs.winehq.org/show_bug.cgi?id=36189

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Austin English  ---
Closing.