August 2004 - Wine-Devel - list.winehq.org

Re: Add some padding in WINPROC_wrapper

by Mike McCormack

Uwe Bonnes wrote: > The problem happens quite early, when the installation wrapper asks for a > location to unzip the file. If the error happens, nothing is displayed. If > the wrapper error doesn't happen. a Messagebox "WebPACK" : To begin the > installation... is displayed. Are you talking about the dialog in the attached screenshot? I have no trouble getting past that screen. InstallShield's wizard starts running for me, and starts copying files. Perhaps the problem is due to a missing registry key or directory? If you'd like I can send you a relay trace to compare. Mike

Aug. 31, 2004

Re: wineserver epoll

by Marcus Meissner

On Tue, Aug 31, 2004 at 11:48:16AM +0300, Shachar Shemesh wrote: > Mike Hearn wrote: > > >>Building with a recent glibc and running on an older one is not > >>supported by glibc, and it won't work for many reasons having nothing > >>to do with epoll. Crossover runs everywhere because it is built > >>against a very old glibc. > > > > > >To clarify, it is possible to build against a new glibc and have it > >run on older libcs, but the process is far from intuitive and requires > >special tools, header overrides etc. We do this in autopackage, and it > >works, but it's quite tricky to get right. > > > >So I guess Shachar could use dlopen, or possibly the epoll functions > >are weak symbols - quite a lot of glibc functions are these days. In > >that case you can just mark them with the weak attribute and that's no > >problem. > > Details, please. How do I do that? Guys, pretty pretty please, just use the glibc function, add a regular configure check and use it if it does not return -ENOSYS. All this confusing handling of dlopening etc etc is way overblown. Ciao, Marcus

Aug. 31, 2004

Re: Add some padding in WINPROC_wrapper

by Mike McCormack

Uwe Bonnes wrote: > any ideas how to pinpoint that problem? Any debug output you need? I tried installing WebPACK_42wp30_full_installer.exe, but it seemed to have other problems. Are you installing it on the Wine CVS? Did you install other software into your ~/.wine first ? Mike

Aug. 31, 2004

Re: Add some padding in WINPROC_wrapper

by Mike McCormack

Uwe Bonnes wrote: > Changelog > windows/winproc.c: WINPROC_wrapper > Add some padding between saved registers and the winproc > arguments. Some winprocs may trash the register area. > > As Mike Hearn suggested, adding some padding helped with my problem with > WebPACK_42wp30_full_installer.exe. I hope, I found the right way to add that > padding. It may work for one application, but it doesn't look like a propper fix. I'd suggest there's probably something else going on that's causing stack corruption. Mike

Aug. 31, 2004

Re: regression: listbox stays disabled in created dialog-window

by Rein Klazes

On Tue, 31 Aug 2004 00:38:30 +0200 (EET), you wrote: > The [1] patch brings some regression. I have filled a bugreport: [2]. > > Here are two png screenshots: [3] [4], one made before the patch is > applied, another made after the patch is applied. > > > [1] http://www.winehq.org/hypermail/wine-cvs/2004/08/0341.html > [2] http://bugs.winehq.org/show_bug.cgi?id=2454 > [3] http://bugs.winehq.org/attachment.cgi?id=681&action=view > [4] http://bugs.winehq.org/attachment.cgi?id=682&action=view > Well, Pegasus Mail has the same problem with lists. And it is fatal: no mail in any mailbox is visible. The configuration dialog of Agent news reader has yet another problem, disappearing buttons: http://home.wanadoo.nl/wijn/tmp/shot1.png before http://home.wanadoo.nl/wijn/tmp/shot2.png after Rein. -- Rein Klazes rklazes(a)xs4all.nl

Aug. 31, 2004

Re: Add some padding in WINPROC_wrapper

by Uwe Bonnes

>>>>> "Mike" == Mike McCormack <mike(a)codeweavers.com> writes: Mike> Uwe Bonnes wrote: >> The problem happens quite early, when the installation wrapper asks >> for a location to unzip the file. If the error happens, nothing is >> displayed. If the wrapper error doesn't happen. a Messagebox >> "WebPACK" : To begin the installation... is displayed. Mike> Are you talking about the dialog in the attached screenshot? I Mike> have no trouble getting past that screen. InstallShield's wizard Mike> starts running for me, and starts copying files. Without the patch, I don't get to that dialogue, Mike> Perhaps the problem is due to a missing registry key or directory? Mike> If you'd like I can send you a relay trace to compare. Please do so. -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Aug. 31, 2004

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

by Mike Hearn

> 2) After you've reduced a thread or process's priority, it's not > possible to elevate it to the original level again (without being root), > so if a thread is set to low priority temporarily, it won't be possible > to restore it to normal priority under Linux. Under Windows it's of > course possible. Other solution is just to detect this and ask the user to rerun Wine as root. I don't think that'd be a big deal.

Aug. 31, 2004

Re: Add some padding in WINPROC_wrapper

by Uwe Bonnes

>>>>> "Mike" == Mike McCormack <mike(a)codeweavers.com> writes: Mike> Uwe Bonnes wrote: >> any ideas how to pinpoint that problem? Any debug output you need? Mike> I tried installing WebPACK_42wp30_full_installer.exe, but it Mike> seemed to have other problems. Are you installing it on the Wine Mike> CVS? Did you install other software into your ~/.wine first ? I have tried on several machines, all with slightly modified trees, but nothing that should influence the behaviour. All machines showed the same error. The problem happens quite early, when the installation wrapper asks for a location to unzip the file. If the error happens, nothing is displayed. If the wrapper error doesn't happen. a Messagebox "WebPACK" : To begin the installation... is displayed. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Aug. 31, 2004

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

by Ove Kaaven

tir, 31.08.2004 kl. 05.23 skrev michael(a)cherryblossom.homelinux.com: > On Mon, Aug 30, 2004 at 08:52:04AM +0200, Ove Kaaven wrote: > > It's not. Linux only allows non-root processes to reduce its priority, > > not increase it, even for non-real-time priorities. Windows, however, > > allows it for non-real-time priorities. > > So the current priority would be the highest priority supported by the > user or process, unless running as root. Hm. Maybe, if you want to look at it that way... > And I suppose that non-root processes can't decrease priority of other > processes (that aren't threads of said process) owned by the user it's > running under to simulate a higher-priority, or that it would be a bad > idea, right? It's possible, but it would be a bad idea for two reasons. 1) It'd mean that everything the user runs would on average get a lower scheduling priority than things run by other users. That's not necessarily what we want. 2) After you've reduced a thread or process's priority, it's not possible to elevate it to the original level again (without being root), so if a thread is set to low priority temporarily, it won't be possible to restore it to normal priority under Linux. Under Windows it's of course possible. > Does renice count as a process run under said user that > changes the priority of a process? I don't understand the question. > I suppose there's also the idea of having a single root process or > daemon (probably which would be an optional component) to "increase > performance" by "allowing wine to increase it's priority" by sending the > a said process or daemon a message or signal to tell it to increase the > priority of (a) wine process(es). Of course, if this is a reality, then > we have to debate over whether we want this installed by default, how it > would be configured, communication mechanisms (i.e. Signals, such as > USRSIG1, Unix Sockets, or IP Sockets), coding style, how interrupts and > whatnot are handled, how the daemon can be efficcently designed... And > then what about people who complain about having too many daemons to > configure and run on their Linux system to do basic tasks... We've toyed with the idea. > What about emulating this increasible priority, at the risk of lowering > wine's performance? Keep the actual real linux priority the same, but > do sleep cycles or slow down the process in some way so that by default > processes run at "Normal", at like, say, 75% (or whatever is the > accepted Windows computed CPU usage) of the thread's assigned/capable > processing power, and then "Idle" or "Low" only running if no other > threads (within wine, or in general) are using the CPU, and then "High" > using 100% of the thread's power? Or are you guys already saying this? The only reliable way to force a sleep cycle is by sending signals. But that's something I suggested in my other post. Note that Windows doesn't compute CPU usage. It just assigns all available CPU time to the highest priority thread that isn't sleeping (doing a round-robin only if there's more than one thread on that priority level), whether it's real-time-priority or idle priority.

Aug. 31, 2004

Re: Add some padding in WINPROC_wrapper

by Mike Hearn

> It may work for one application, but it doesn't look like a propper fix. > I'd suggest there's probably something else going on that's causing > stack corruption. Probably it was declared with the wrong calling convention. Windows deals with this transparently but perhaps more transparently than us :) So the question is: what calling conventions could cause the observed behaviour?

Aug. 31, 2004