What does not
Sometimes gets stuck when loading dlls.
Probably handling of debug events within debugger loop which might trigger APC to wineserver while the target's threads are suspended (APC fails to be executed, blocking caller = debugger).
Needs further investigation ...
What was not tested
This is early alpha release of debugger version 2.0
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Fedora 9||Oct 26 2008||1.1.7||Yes||Yes||Bronze||Anastasius Focht|
When the disassembly window goes blank (after pausing, single stepping into wine, etc.) you probably hit a code location which the debugger can't properly handle due to design of Wine/Linux.
The debugger encounters ELF code in wine builtins outside of win32 API virtual mapping range which leads to empty code/disassembly window (debugger needs to read memory in order to disassemble it). You can see EIP still changing while stepping (registers window) but no code is actually displayed.
Just hit a few "run until return" until the code reaches PE virtual mapping range. The code/disassembly will appear again. This is expected behaviour and by design.ÂÂ
You most likely hit bug 14697. Open another console and kill everything.
$ wineserver -k
Use WinetricksÂ'corefonts' to take care of this problem, it will fix the display of text in disassembly, memory views and the likeÂ
$ bash winetricks corefonts