WINEDEBUG output issues
Paul Vriens
paul.vriens.wine at gmail.com
Wed Aug 15 03:53:03 CDT 2007
Hi,
I was trying to read a '+all,+relay,-syslevel,-gdi,-font' trace but several
lines show something like:
000d:Cget_window_property000d:Call0x000d:, atom=000d:Call
usePropertySheetInfo000d000000d:Call user32.CharNextA(0 {000d:Call
user32.CharNextA(0040a04d "les\\Nmap") ret=0040551c
The above is output from the same thread. I also have:
0009:trace:heap:RtlAllocateHeap (0x110000,00000002,0000014000d:Call
user32.CharNe0009:trace:dc:GetDCState (0x474): retu000d:Ret user32.CharNextA()
retval=004093c6 ret=0040551c
Which mixes threads.
Debug traces can already be hard to read but this is even more confusing.
Any idea what the cause is (or better, the solution)?
Cheers,
Paul.
More information about the wine-devel
mailing list