http://bugs.winehq.org/show_bug.cgi?id=19659
--- Comment #27 from Jarod wine@faltine.com 2010-03-04 15:38:30 --- Created an attachment (id=26607) --> (http://bugs.winehq.org/attachment.cgi?id=26607) crash after login with wine-1.1.18-301-g014c4bf
I only recently started to witness a crash right after login into the game. the backtrace is similar to one posted above, and it looks like it happened in the same situation. This test was done with version 1.1.18-301-g014c4bf: looks like there are at least two different crashes with the first regression ?
fixme:d3d:buffer_Map count 1WINED3D_BUFFER_DIRTY trueReturning memory at 0x12869580 (base 0x12869580, offset 0) fixme:d3d:buffer_Map iface 0x111945e8, offset 0, size 5268, data 0xa6ce7d0, flags 0 fixme:d3d:buffer_Map count 1WINED3D_BUFFER_DOUBLEBUFFER=false and This->buffer_objectBefore GL_EXTCALL1wine: Unhandled page fault on read access to 0x00000764 at address 0x613864f2 (thread 0025), starting debugger... Unhandled exception: page fault on read access to 0x00000764 in 32-bit code (0x613864f2).
I added some fixme lines in buffer.c. I put the complete buffer.c at the start of the log file, but here is an exerpt:
FIXME("Before GL_EXTCALL1"); GL_EXTCALL(glBindBufferARB(This->buffer_type_hint, This->buffer_object)); FIXME("Before GL_EXTCALL2"); This->resource.allocatedMemory = GL_EXTCALL(glMapBufferARB(This->buffer_type_hint, GL_READ_WRITE_ARB)); FIXME("After GL_EXTCALL2");
The crash happens during the first of the two GL_EXTCALL instructions.
Does it help ? I will try to do the same thing for the others crashes too.