http://bugs.winehq.org/show_bug.cgi?id=11231
--- Comment #8 from Jörg Höhle hoehle@users.sourceforge.net 2008-01-25 04:05:20 --- Oddly, $ WINEDEBUG=trace+gdi make test does not report any glibc error (0.9.53 source tree). Instead I see: [...] trace:gdi:GDI_ReleaseObj (0x1d8): leave 1 wine: Unhandled page fault on write access to 0x00000000 at address 0x601ae335 (thread 0009), starting debugger... Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x601ae335). =>1 0x601ae335 cfree+0x75() in libc.so.6 (0x0034f548) 2 0x60b7ebdb _mesa_free+0x1d() in i915_dri.so (0x0034f558) 3 0x60c34716 _mesa_delete_program+0x26() in i915_dri.so (0x0034f578) 4 0x60c35d25 _mesa_DeletePrograms+0x131() in i915_dri.so (0x0034f5a8) 5 0x60ab030d glDeleteProgramsARB+0x31() in libgl.so.1 (0x0034f5c8) 6 0x64b6a9e8 IWineD3DImpl_FillGLCaps+0x8051(gl_info=0x64c05f4c) [.../wine/dlls/wined3d/directx.c:448] in wined3d (0x0034f768) 7 0x64b6fda9 InitAdapters+0x1ee7() [.../wine/dlls/wined3d/directx.c:3097] in wined3d (0x0034fb88)
I remember in the past (in a different context) already observing different behaviour between using or not WINEDEBUG. How comes? What must one consider in order not to interfere with program execution?