WineConf agenda

[Jacek Caban]

Hi all,


It's getting close to WineConf and I think it's time to think about 
agenda. Does anyone have anything he'd like to talk about? Any ideas 
about conversations we should have? Feel free to add them to 
https://wiki.winehq.org/WineConf2017


Cheers,
Jacek

[Alex Henrie]

2017-10-13 5:23 GMT-06:00 Jacek Caban <jacek(a)codeweavers.com>:
> It's getting close to WineConf and I think it's time to think about agenda.
> Does anyone have anything he'd like to talk about? Any ideas about
> conversations we should have? Feel free to add them to
> https://wiki.winehq.org/WineConf2017

It would be nice to talk about the fake DLL problem. In case you're
not familiar, numerous popular applications (Chrome, Steam, StarCraft,
Overwatch...) manually load system DLLs into memory, do some
verification checks, and then attempt to jump into the DLL's code.
This causes a crash because Wine's DLLs are fakes that don't contain
the actual function code. Wine Staging has a solution to the problem
involving making the fake DLLs more realistic and then catching and
redirecting attempts to execute memory-mapped code. I'm curious to
know what it would take to get the Wine Staging solution or another
reasonable solution into mainline Wine.

-Alex

[Marcus Meissner]

On Mon, Oct 23, 2017 at 12:18:27AM -0600, Alex Henrie wrote:
> 2017-10-13 5:23 GMT-06:00 Jacek Caban <jacek(a)codeweavers.com>:
> > It's getting close to WineConf and I think it's time to think about agenda.
> > Does anyone have anything he'd like to talk about? Any ideas about
> > conversations we should have? Feel free to add them to
> > https://wiki.winehq.org/WineConf2017

How about having a bit more strategy discussion on merging Wine Staging
patches (quicker) to mainline wine?

Ciao, Marcus

[Donat Enikeev]

> How about having a bit more strategy discussion on merging Wine Staging patches (quicker) to mainline wine?

It would be interesting video indeed, I followed several big patch series based on staging and adjusted to be well-qualified (tests, fixes, etc) -- that were moving to the bottom of https://source.winehq.org/patches/ without a comment or response and then disappeared :) Probably there are some non-obvious rules like proof-of-time or code-support concerns or existing plans to implement same functionality in a more correct way -- visibility on the staging->mainline process would be very useful for those, who want to help the project in this way, as clearly staging patches help win applications on the edge and attract attention of potential volunteers  

P.s. At least, it looks as making sense to add to for each patch in staging git, what it is lacking, ideas on better implementation, links to discussions or quotes from there, etc

Best,
Donnie

23.10.2017, 14:00, "Marcus Meissner" <meissner(a)suse.de>:
> On Mon, Oct 23, 2017 at 12:18:27AM -0600, Alex Henrie wrote:
> >  2017-10-13 5:23 GMT-06:00 Jacek Caban <jacek(a)codeweavers.com>:
> >  > It's getting close to WineConf and I think it's time to think about agenda.
> >  > Does anyone have anything he'd like to talk about? Any ideas about
> >  > conversations we should have? Feel free to add them to
> >  > https://wiki.winehq.org/WineConf2017
>
> How about having a bit more strategy discussion on merging Wine Staging
> patches (quicker) to mainline wine?
>
> Ciao, Marcus

[Alex Henrie]

2017-10-23 8:18 GMT+02:00 Alex Henrie <alexhenrie24(a)gmail.com>:
> 2017-10-13 5:23 GMT-06:00 Jacek Caban <jacek(a)codeweavers.com>:
> > It's getting close to WineConf and I think it's time to think about agenda.
> > Does anyone have anything he'd like to talk about? Any ideas about
> > conversations we should have? Feel free to add them to
> > https://wiki.winehq.org/WineConf2017
>
> It would be nice to talk about the fake DLL problem. In case you're
> not familiar, numerous popular applications (Chrome, Steam, StarCraft,
> Overwatch...) manually load system DLLs into memory, do some
> verification checks, and then attempt to jump into the DLL's code.
> This causes a crash because Wine's DLLs are fakes that don't contain
> the actual function code. Wine Staging has a solution to the problem
> involving making the fake DLLs more realistic and then catching and
> redirecting attempts to execute memory-mapped code. I'm curious to
> know what it would take to get the Wine Staging solution or another
> reasonable solution into mainline Wine.

There are at least two open bugs about the fake DLL problem:

https://bugs.winehq.org/show_bug.cgi?id=39403
https://bugs.winehq.org/show_bug.cgi?id=42741

And at least two more that are related:

https://bugs.winehq.org/show_bug.cgi?id=40479
https://bugs.winehq.org/show_bug.cgi?id=37585

-Alex