http://bugs.winehq.org/show_bug.cgi?id=11746
--- Comment #1 from Dan Kegel dank@kegel.com 2008-02-26 17:39:41 --- The stack looked smashed (args both 48), so I ran the server under valgrind. Sure enough, got lots of
==10887== Invalid read of size 4 ==10887== at 0x804B170: filter_from_inode (change.c:579) ==10887== by 0x804C23B: req_read_directory_changes (change.c:872) ==10887== by 0x806B807: call_req_handler (request.c:286) ==10887== by 0x8056563: main_loop (fd.c:437) ==10887== by 0x805A904: main (main.c:138) ==10887== Address 0x4F0E67C is 20 bytes inside a block of size 68 free'd ==10887== at 0x402237F: free (vg_replace_malloc.c:233) ==10887== by 0x804B2FA: free_inode (change.c:475) ==10887== by 0x804B344: free_inode (change.c:457) ==10887== by 0x804C5B1: dir_destroy (change.c:314) ==10887== by 0x805DA5D: release_object (object.c:282) ==10887== by 0x8057EB1: close_handle (handle.c:377) ==10887== by 0x806B807: call_req_handler (request.c:286) ==10887== by 0x8056563: main_loop (fd.c:437) ==10887== by 0x805A904: main (main.c:138)
so the server seems to be referencing freed memory. Tsk.