Hi, I am currently trying to debug an lockup that happens in Planscape:Torment and potentially other Black Isle games(havent tested yet) as well. So far I am out of luck. (For those who know the game the lockup happens between the intro movie and the main menu) The symtoms are: --debugmsg +relay doesnt show the lockup it seems to be timing related and all these debug msg slow it down enough to get past the lockup point --debugmsg +ddraw or +dsound will show the game still drawing and playing sound even though the screen is black and no sound is coming forth anymore no debugger will show up and no timed out msg in WaitForCriticalSection will show so it isnt an uncaught exception or critical section deadlock
My config: Desktop Mode:800x600 Arts Sound Driver XVidMode+,DGA2-,XShm+,DXGrab-,PerfectGraphics+,DoubleBuffered+ Any ideas? I am out of them. While I am at it Is the option +/- relay=<module or function name> still supposed to work? I tried --debugmsg +relay=ntdll or +relay=RtlEnterCriticalSection which didnt produce any output although +relay shows the function and module is used. RFE: Actually I am not interested in debug msgs after the debugger started. Could there be an option that an debugger start turns off debug msgs. When the debugger starts I often get the msg wine: hash.c:392: DEBUG_GetSymbolValue: Assertion 'strlen(name) < sizeof(buffer) - 2' failed. which results in an unhandled exception in the debugger. Whats up with that? Torment shows the msg fixme:ddraw:app didnt request a valid surface type - assuming offscreen plain very often. Shouldnt this be a warn instead of a fixme? Thanks for your time I appreciate it. Enrico Horn [EMAIL PROTECTED]
