gdi32: Don't let the gdi32 driver allocate memory in the dplayx region.
Nikolay Sivov
bunglehead at gmail.com
Fri Jul 26 01:04:59 CDT 2013
On 7/26/2013 08:48, Alexei Svitkine wrote:
>
>
>
> On Mon, Jul 22, 2013 at 10:45 PM, Alexei Svitkine
> <alexei.svitkine at gmail.com <mailto:alexei.svitkine at gmail.com>> wrote:
>
> Don't let the gdi32 driver allocate memory in the dplayx region.
>
> Fixes bug: http://bugs.winehq.org/show_bug.cgi?id=34095
>
> The issue is that the dplayx code in wine needs to allocate some
> memory at a static address (0x50000000) and loading the Mac native gdi
> driver ends up using that part of the address space.
>
> This patch fixes that by reserving that part of memory while the
> display driver is initialized and releasing it after.
>
> ---
> dlls/gdi32/driver.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Please stops resending this. Looks like dplay should be fixed to not
depend on that reserved address area.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20130726/39ac109b/attachment.html>
More information about the wine-devel
mailing list