On Thu, Apr 16, 2009 at 2:28 PM, Austin English <austinenglish@xxxxxxxxx> wrote:
> To list as well:
>
> On Thu, Apr 16, 2009 at 1:26 AM, Ben Lau <xbenlau@xxxxxxxxx> wrote:
>> WINEDEBUG="warn+all" wine ./Evernote.exe 2>&1 | tee log
>
> Why are you using warn+all? I'm curious, since it seems to be a
> popular myth that it helps...
>
>> Soon Evernote launched the UI, wine quit (forked a new process?) and
>> no more message printed..
>
> Just attach the plain output, without WINEDEBUG.
>
On Thu, Apr 16, 2009 at 2:27 PM, Austin English <austinenglish@xxxxxxxxx> wrote:
> On Thu, Apr 16, 2009 at 1:26 AM, Ben Lau <xbenlau@xxxxxxxxx> wrote:
>> WINEDEBUG="warn+all" wine ./Evernote.exe 2>&1 | tee log
>
> Why are you using warn+all? I'm curious, since it seems to be a
> popular myth that it helps...
>
>> Soon Evernote launched the UI, wine quit (forked a new process?) and
>> no more message printed..
>
> Just attach the plain output, without WINEDEBUG.
>
>
> --
> -Austin
>
Without the WINEDEBUG option , only 5 lines are printed. As I am not
familiar with wine , I just think it could print out more message...
Anyway , the plain output is attached:
$ wine ./Evernote.exe
fixme:thread:NtQueryInformationThread Cannot get kerneltime or
usertime of other threads
fixme:msg:ChangeWindowMessageFilter 4a 00000001
fixme:msg:ChangeWindowMessageFilter c073 00000001
err:ole:CoGetClassObject class {aac46a37-9229-4fc0-8cce-4497569bf4d1}
not registered
err:ole:CoGetClassObject no class object
{aac46a37-9229-4fc0-8cce-4497569bf4d1} could be created for context
0x1
