July 2003 - Wine-Devel - list.winehq.org

Re: Expect deadlock!

by Mike Hearn

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(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

July 30, 2003

Re: Unhandled exception (wine-20030709)

by Magnus Solvang

Quoting Mike Hearn (mike(a)theoretic.com) | Looks like an NPTL problem, I'd avoid using testing series kernels | unless you know what you're doing WRT threading technologies, otherwise | it's going to be a world of pain...... Thank you, Mike! I checked my config.log, and it was indeed compiled --with-nptl (I just used ./tools/wineinstall the first time). Using just ./configure -C --prefix=/usr/local, and then starting ./tools/wineinstall worked like a charm. notepad.exe started fine now. :) "make depend && make" crashed on audio.c, though. Only wineinstall made it through. - M

July 30, 2003

Expect deadlock!

by Marcelo Duarte

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! -- Marcelo Duarte

July 30, 2003

Re: fontview.exe...

by Marcelo Duarte

I think that is interesting... when I aquire fonts like urwfonts.zip and want to see the fonts in Winzip, then use fontview. And, remember to modify the registry.... good luck. Em Sáb 26 Jul 2003 10:21, Jonathan Wilson escreveu: > Its used by windows to display fonts before and after installation. > And I know of at least one setup program (might have been a Corel app, I > forget) that displays a long list of fonts which you can select from to > install and then uses fontview.exe (I think its fontview.exe, it loks very > similar anyhow) for previewing the fonts (so you can see what they look > like before they are installed). > > Anyone want to comment on this: > 1.does anyone else remeber the app and/or the dialog? > 2.does anyone know if it really is fontview.exe? > 3.does wine need a fontview.exe? > and 4.if I was to code a fontview.exe, would it be of use to anyone (wine, > reactos etc)? -- Marcelo Duarte

July 30, 2003

Strange behavior on build

by David D. Hagood

I'm having a strange behavior trying to build Wine on my machine at work (which is a modified RH7.3 machine): First of all, if I attempt to do a standard CVS checkout followed by a make depend, the make depend failes with a "dlls - no such directory" error, even though it exists. Changing SHELL=/bin/sh to SHELL=/bin/bash in Make.rules and re-running configure fixes this, but then I get stuck in a loop building - it looks like the makefile starts building the dependancy "wine", then builds "libs", then decides it needs to build "wine" to build "libs" and starts that, then builds "libs".... I'm at a bit of a loss to explain the behavior, so does anybody have any good suggestions? Versions: GNU bash, version 2.05b.0(1)-release (i586-redhat-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc. GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i386-redhat-linux-gnu Linux version 2.4.20-openmosix1 (root@(none)) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)) #1 Sun Jan 12 04:18:51 CST 2003 (if you would be so kind, please copy my work address of David decimalpoint Hagood ('A'-1) aeroflex decimalpoint com since I am only subscribed to the list on my personal email).

July 29, 2003

Re: Profiling wine

by Ove Kaaven

tir, 29.07.2003 kl. 13.55 skrev Jeremy White: > > How about giving oprofile a spin ? > > > > It is very good at pinpointing runtime hotspots. I just wanted to give > > a suggestion on how to get going with profiling right now without the > > need to wait for wineprofile functionality. > > I'm told (and have been persuaded of this), that Wine's internal > structures preclue a 'normal' profiler from working properly, > hence the need for a Wine specific one. Then again, oprofile is not a normal profiler, it's a kernel-based one. I've tried it, it "works", but it seems that it requires a 2.5 kernel in order to be really useful (it's not able to generate call graphs with 2.4)

July 29, 2003

Re: Unhandled exception (wine-20030709)

by Mike Hearn

Looks like an NPTL problem, I'd avoid using testing series kernels unless you know what you're doing WRT threading technologies, otherwise it's going to be a world of pain...... On Tue, 2003-07-29 at 23:03, Magnus Solvang wrote: > (I posted this to the wine-users-list a week ago, but didn't get > any respons) > > I just tried to install wine for my first time. Redhat 9.0, kernel > 2.5.73. Downloaded the rpm-binary, but when trying to start > notepad.exe, it looped with a message like: > > wine: Unhandled exception (thread 01f9), starting debugger... > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > > While looping it started nearly 255 processes (max PTYs?), before the > machine halted. I did this before modifying my config-file (using > the default one). > After adjusting the config-file, I no longer got any error-messages, > but the same thing happened. > > [...] > wine: Unhandled exception (thread 01f1), starting debugger... > wine: Unhandled exception (thread 01f3), starting debugger... > wine: Unhandled exception (thread 01f5), starting debugger... > wine: Unhandled exception (thread 01f7), starting debugger... > wine: Unhandled exception (thread 01f9), starting debugger... > wine: Unhandled exception (thread 01fb), starting debugger... > > Fine! I then tried to compile wine from source, but at the end of > the installation (su root/make install - wine only), the same thing > happened: > > [...] > wine: Unhandled exception (thread 01f5), starting debugger... > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > Could not stat /cdrom (No such file or directory), ignoring drive D: > wine: Unhandled exception (thread 01f7), starting debugger... > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > Could not stat /cdrom (No such file or directory), ignoring drive D: > wine: Unhandled exception (thread 01f9), starting debugger... > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > Could not stat /cdrom (No such file or directory), ignoring drive D: > wine: Unhandled exception (thread 01fb), starting debugger... > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > Could not stat /cdrom (No such file or directory), ignoring drive D: > wine: Unhandled exception (thread 01fd), starting debugger... > ./tools/wineinstall: line 645: 26966 Killed $REGEDIT $DEFREG >/dev/null > Registry install failed. > > I managed to open a terminal and do a "killall -9 wine". This happened > during "make install", so I didn't get to edit the config-file before > this happened. > > I have tried booting with both 2.4 and 2.5-kernels, with the same > result. > > - M >

July 29, 2003

Unhandled exception (wine-20030709)

by Magnus Solvang

(I posted this to the wine-users-list a week ago, but didn't get any respons) I just tried to install wine for my first time. Redhat 9.0, kernel 2.5.73. Downloaded the rpm-binary, but when trying to start notepad.exe, it looped with a message like: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: While looping it started nearly 255 processes (max PTYs?), before the machine halted. I did this before modifying my config-file (using the default one). After adjusting the config-file, I no longer got any error-messages, but the same thing happened. [...] wine: Unhandled exception (thread 01f1), starting debugger... wine: Unhandled exception (thread 01f3), starting debugger... wine: Unhandled exception (thread 01f5), starting debugger... wine: Unhandled exception (thread 01f7), starting debugger... wine: Unhandled exception (thread 01f9), starting debugger... wine: Unhandled exception (thread 01fb), starting debugger... Fine! I then tried to compile wine from source, but at the end of the installation (su root/make install - wine only), the same thing happened: [...] wine: Unhandled exception (thread 01f5), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f7), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fb), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fd), starting debugger... ./tools/wineinstall: line 645: 26966 Killed $REGEDIT $DEFREG >/dev/null Registry install failed. I managed to open a terminal and do a "killall -9 wine". This happened during "make install", so I didn't get to edit the config-file before this happened. I have tried booting with both 2.4 and 2.5-kernels, with the same result. - M

July 29, 2003

Re: API tracking and documentation

by Steven Edwards

--- Francois Gouget <fgouget(a)free.fr> wrote: > Patrik Stridvall wrote some code in winapicheck that makes it quite > simple to do something relatively similar to the above. What's best, no > new information is needed in the Wine sources. Check the following page > for more details: > > http://fgouget.free.fr/wine/winapi_stats-en.shtml It looks good. The only issue is that winapi depends on perl and we are trying not make our build and documentation system depend on to many external libs. Our focus with WINE ATM is getting the WINE dlls in a good enough shape to build with Mingw headers so we can directly import them in to our source tree and the current API tracking system we have is part of that build system. I dont think adding perl to list of depends will go well with our developers. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

July 29, 2003

Re: Trackbar size fixes

by Duane Clark

Duane Clark wrote: > Duane Clark wrote: > >>Hmm, attached is what that looks like for me. So I don't know why it >>looks bad to you. > > > > Oops, sorry. I was using a native control there. I do see the same thing > as you. (Sorry about replying to myself several times) As BiGgUn suggests, in TRACKBAR_InitializeThumb, setting: infoPtr->uThumbLen = 21; fixes IE. I suspect that is close to correct, other than that it probably should not be a magic number.

July 29, 2003