With all the known purify problems eliminated (not including savegames),
tracking down what's going wrong on win32 fullscreen support is a bit
easier. Everything points to gfx_crossblit.c, line 60. There is one byte
past the end of priority_buffer that is read.
Call stack follows:
gfx_crossblit_32_P [gfx_crossblit.c:60]
gfx_crossblit_pixmap [gfx_support.c:370]
sdl_draw_pixmap [sdl_driver.c:642]
gfxop_draw_pixmap [operations.c:249]
gfxop_draw_cel_buffer [operations.c:1690]
gfxop_draw_cel [operations.c:1698]
gfxwop_dyn_view_draw [widgets.c:860]
gfxwop_container_draw_contents [widgets.c:1397]
gfxwop_sorted_list_draw [widgets.c:1619]
gfxwop_port_draw [widgets.c:1993]
It's kind of hard for me to properly debug this, since FreeSCI grabs
control of the framebuffer in fullscreen. When I set a breakpoint or
purify breaks, I can't see the debugger to figure out what's going on.
I can add print statements to help, just let me know.
--
http://www.clock.org/~matt
