Logging issue ?

[GOUJON Alexandre]

Hi,

To understand why a game does not work with the disc while it does with 
the ISO (created from the same disc), I made a log with 
+tid,+relay,+volume in both cases and noticed :

- some lines (call or ret) are not printed / missing
- some lines are half-printed and joined with the following

I know sometimes a trailing \n is missing in TRACE() so the output is 
uncertain.
But that doesn't seem to be the case here.

Maybe it's not thread safe or something like that ?
I tried using taskset 1 wine .. to force using one core but no luck.

Here a small part of my log (order not modified, I just remove lines 
from other threads):
0030:Call KERNEL32.GetVolumeInformationA(09732288 
"D:",097321ec,0000007f,00000000,00000000,097321d8,00000000,00000000) 
ret=0057b045
0030:trace:volume:GetVolumeInformationW L"\??\D:\": found fs type 
50009:Call wined3d.wined3d_mutex_unlock() ret=7ed6e3a6
0030:Ret  KERNEL32.CreateFileA() retval=000001f4 ret=00c8b5ab
0030:Call 
KERNEL32.DeviceIoControl(000001f4,00041018,00000000,00000000,09732190,00000008,097321a4,00000000) 
ret=00c8b64a

The game calls GetVolumeInformationA .. the trace is mixed with output 
of another thread .. I guess the game open the device (no call line) .. 
and then do some ioctl.
No trace of how the game opened the device..

I can do several logs and try to compare each other to have a complete 
puzzle but that's not very handy.

Any thought ? idea ? advice ?

(I'm using packaged wine on x86_64)

Thanks

[Nikolay Sivov]

On 5/18/2012 17:23, GOUJON Alexandre wrote:
> Hi,
>
> To understand why a game does not work with the disc while it does 
> with the ISO (created from the same disc), I made a log with 
> +tid,+relay,+volume in both cases and noticed :
> - some lines (call or ret) are not printed / missing
> - some lines are half-printed and joined with the following
>
> I know sometimes a trailing \n is missing in TRACE() so the output is 
> uncertain.
> But that doesn't seem to be the case here.

No, it's not a case.
> Any thought ? idea ? advice ?

I believe there was a discussion about that in the past, It usually 
helps to use a ">>" redirect that appends to log file instead of 
replacing its contents. But you'll obviously need to clean a log file 
before starting anything
> (I'm using packaged wine on x86_64)
>
> Thanks