#wine-staging

why the new "winehq-staging" package?

ivan: it just replaced the old compat package

DarkPlayer: ah, thanks

just realized the same after extracting the debs :-)

we are also working on builds for the development branch of wine and since the name wine-devel/development/dev is already used by a lot of distros, we took winehq-devel

and in order to have a somewhat similar naming between wine-staging and wine-devel, we renamed the compat package to winehq-staging

hey

i'm running mesa llvmpipe on 64-bit windows, plug wine with primitive drawing disabled by a 'return;'

applying CSMT patches doubles the performance of the software in 2D menu mode to FPS, but once it goes into flight simulator with full 3D, FPS drop to 20

they're 50-60 without CSMT patches

that is, only using libwine, wined3d and d3d9

[06winetricks/master][05d1c5fb2](00http://is.gd/451fLC) 02Austin English: vcrun2015: install a few more dlls. Based on a patch by rboxeur.

slackner, DarkPlayer: Comment #8 of https://bugs.winehq.org/show_bug.cgi?id=35975 seems to report a regression in Staging compared to Wine Devel

04Bug 35975: normal, P2, 1.8.0, wine-bugs, STAGED , Comanche 3 shows only gray screen

Has anyone thought of using something like DynamoRIO to replace ptrace in wine?

ryao: ptrace is used in some performance critical parts in wine, so you want to keep the overhead small

DarkPlayer: Someone was asking me about sandboxing Gentoo Portage's src_install phase. One of the ideas that occurred to me was DynamoRIO. Basically, it is a tool that lets you instrument code so that it calls library code you load and to make sure that it cannot touch that code except through the methods you specify.

DarkPlayer: i.e. you can use things like shmem to emulate a kernel from userspace that is protected from the code being executed.

DarkPlayer: It was covered in a graduate security class. The technique uses is solid.

ryao: the application running in wine could still do syscalls and hooking all of them would make the application very slow

DarkPlayer: You don't have to hook all of them.

DarkPlayer: Just the ones that interest you... actually for windows, that is all of them.

ptrace does the same thing though, doesn't it? Wait... you are relying on a custom libc to do that (I think). DynamoRIO doesn't buy you anything there.

DarkPlayer: Its main benefit would be a way to avoid ptrace.

wine uses ptrace only to make windows debuggers work, i.e. to provide the necessary access to other threads and processes

for other stuff that needs emulation, it catches the according signal

DarkPlayer: Ah, okay. THanks.

how can I apply the patches from staging to the development HEAD making each patch a commit?

c_korn: /path/to/wine-staging/patches/patchinstall.sh --backend=git --force-autoconf --all

the first param can be used to create separate commits

and force-autoconf will also include autogenerated changes in each commit, which makes it easier to bisect

slackner: hm. was using git-apply. seems this does not create commits. this patch fails to apply now: Pipe/0005-kernel32-tests-Add-tests-for-closing-named-pipes.patch

c_korn: yes, "git-apply" does not create separate commits, only "git" or "git-am"

c_korn: and the other problem is caused by the fact that currently wine-staging is a couple of commits behind the development branch

yeah, but "git" was not listed here: https://github.com/wine-compholio/wine-staging/...

should I run "git am --skip" ?

c_korn: i know, but its still supported ;) its a shortcut for "git-am"

c_korn: you should check out b5c0c46cfc0c8590d797d8cbe08b3f0a8cfe751e before running the script

c_korn: see https://github.com/wine-compholio/wine-staging/...

ok, that worked slackner. now let's see if my local build of staging has the same issue.

slackner: the local compilation of wine-staging also works. problem seems to be related to the Debian package somehow

c_korn: well, as you mentioned, this app depends a lot on the exact compilation parameters

c_korn: when building packages, there are a lot of additional steps involved.. exact optimization flags, stripping debug symbols, ...