Hi all,
Somebody could help saying me what it means the messages below and where I must look for to finish with them?
Thank you!
err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock!
I'd like to know this too. Spending ten minutes on Google revealed little - all references to syslevels in the context on Win32 pointed back to WineHQ, so it seems to be either undocumented (likely) or a Wine internal thing (from the name of the functions, I'd guess that it's undocumented MS stuff).
In particular, this error occurred today while doing a demo for my boss (he knew this particular action would cause a freeze/crash but he wanted to see what it would do under Wine). He wanted to know what it meant, and obviously I couldn't really tell him.
It seems to be something to do with locking 16 bit parts of the code, and I found an email from Andi Mohr talking about "syslevel violations being an ongoing problem". Level 3 is "GDI Level", but I don't know what level 2 is. The relevant file (scheduler/syslevel.c) is no help at all.
On Wed, 2003-07-30 at 06:05, Marcelo Duarte wrote:
Hi all,
Somebody could help saying me what it means the messages below and where I must look for to finish with them?
Thank you!
err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock!
Hum.... Well, I know in my program when this happen. If I run wine --debugmsg +gdi I can folow the problem? What are your sugestion? Thank you. ----- Original Message ----- From: "Mike Hearn" m.hearn@signal.qinetiq.com To: "Marcelo Duarte" wine-devel@bol.com.br Cc: wine-devel@winehq.com Sent: Wednesday, July 30, 2003 12:48 PM Subject: Re: Expect deadlock!
I'd like to know this too. Spending ten minutes on Google revealed little - all references to syslevels in the context on Win32 pointed back to WineHQ, so it seems to be either undocumented (likely) or a Wine internal thing (from the name of the functions, I'd guess that it's undocumented MS stuff).
In particular, this error occurred today while doing a demo for my boss (he knew this particular action would cause a freeze/crash but he wanted to see what it would do under Wine). He wanted to know what it meant, and obviously I couldn't really tell him.
It seems to be something to do with locking 16 bit parts of the code, and I found an email from Andi Mohr talking about "syslevel violations being an ongoing problem". Level 3 is "GDI Level", but I don't know what level 2 is. The relevant file (scheduler/syslevel.c) is no help at all.
On Wed, 2003-07-30 at 06:05, Marcelo Duarte wrote:
Hi all,
Somebody could help saying me what it means the messages below and where
I
must look for to finish with them?
Thank you!
err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0,
level 3.
Expect deadlock!
-- Mike Hearn m.hearn@signal.qinetiq.com QinetiQ - Malvern Technology Center
When attempting to install Office 2000 under the latest wine from cvs, It stops half way through the installation with the following error.
err:cabinet:FDICopy FDIIsCabinet failed. Any ideas?
On Thursday 31 July 2003 02:57 pm, Boris wrote:
When attempting to install Office 2000 under the latest wine from cvs, It stops half way through the installation with the following error.
err:cabinet:FDICopy FDIIsCabinet failed. Any ideas?
This rollup of the recent cabinet patches should fix it.
-- gmt
-
Boris -
Gregory M. Turner -
Marcelo Duarte -
Mike Hearn