September 2013 - Wine-Devel

Re: [PATCH 3/5] wined3d: Introduce a function to initialize swapchain specific device state.
by Alexandre Julliard Sept. 24, 2013

Sept. 24, 2013

Henri Verbeet <hverbeet(a)codeweavers.com> writes: > --- > dlls/wined3d/device.c | 51 +++++++++++++++++---------------------------- > dlls/wined3d/stateblock.c | 5 +---- > 2 files changed, 20 insertions(+), 36 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -M dxgi.dll -T ../../.. -p dxgi_test.exe.so device.c && touch device.ok wine: Unhandled page fault on read access to 0x0000002c at address 0x686aa077 (thread 004f), starting debugger... Unhandled exception: page fault on read access to 0x0000002c in 32-bit code (0x686aa077). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:686aa077 ESP:0032f890 EBP:0032f978 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:6879e6d0 ECX:0032f9e0 EDX:00000000 ESI:0014e23c EDI:00000000 Stack dump: 0x0032f890: 00000001 00000001 00000000 567a5784 0x0032f8a0: 0000851a 00000000 00008058 00000001 0x0032f8b0: 00000001 00000001 00000000 00000000 0x0032f8c0: 0000001e 00000012 0032f9ec 00000000 0x0032f8d0: 00000001 00000000 00000000 00000000 0x0032f8e0: 00000000 7e0bd298 0032f9ec 00008035 Backtrace: =>0 0x686aa077 device_clear_render_targets+0x77(device=0x142208, rt_count=0x8, fb=0x14e23c, rect_count=0, rects=(nil), draw_rect=0x32f9e0, flags=0x1, color=0x6875e2bc, depth=1.000000, stencil=0) [/home/julliard/wine/wine/dlls/wined3d/device.c:219] in wined3d (0x0032f978) 1 0x686b0b67 wined3d_device_clear+0x136(device=0x142208, rect_count=0, rects=(nil), flags=0x1, color=0x6875e2bc, depth=1.000000, stencil=0) [/home/julliard/wine/wine/dlls/wined3d/device.c:3501] in wined3d (0x0032fa08) 2 0x686b613c wined3d_device_init_3d+0x3fb(device=<couldn't compute location>, swapchain_desc=<couldn't compute location>) [/home/julliard/wine/wine/dlls/wined3d/device.c:940] in wined3d (0x0032fa98) 3 0x6864d008 dxgi_factory_CreateSwapChain+0x127(iface=<couldn't compute location>, device=<couldn't compute location>, desc=<couldn't compute location>, swapchain=<couldn't compute location>) [/home/julliard/wine/wine/dlls/dxgi/factory.c:232] in dxgi (0x0032fb38) 4 0x6862b5aa func_device+0x13f9() [/home/julliard/wine/wine/dlls/dxgi/tests/../../../include/dxgi.h:2037] in dxgi_test (0x0032fcf8) 5 0x6862c165 run_test+0x144(name=<is not available>) [/home/julliard/wine/wine/dlls/d3d10core/tests/../../../include/wine/test.h:570] in dxgi_test (0x0032fd48) 6 0x68629c23 main+0x152(argc=<is not available>, argv=<is not available>) [/home/julliard/wine/wine/dlls/d3d10core/tests/../../../include/wine/test.h:640] in dxgi_test (0x0032fe08) 7 0x6862cbb0 __wine_spec_exe_entry+0x7f(peb=<couldn't compute location>) [/home/julliard/wine/wine/dlls/winecrt0/exe_entry.c:36] in dxgi_test (0x0032fe58) 8 0x7b85f36c call_process_entry+0xb() in kernel32 (0x0032fe78) 9 0x7b86054b start_process+0x6a(peb=<couldn't compute location>) [/home/julliard/wine/wine/dlls/kernel32/process.c:1084] in kernel32 (0x0032feb8) 10 0x7bc7fd50 call_thread_func_wrapper+0xb() in ntdll (0x0032fed8) 11 0x7bc82c5d call_thread_func+0x7c(entry=0x7b8604e0, arg=0x7ffdf000, frame=0x32ffc8) [/home/julliard/wine/wine/dlls/ntdll/signal_i386.c:2602] in ntdll (0x0032ffa8) 12 0x7bc7fd2e call_thread_entry_point+0x11() in ntdll (0x0032ffc8) 13 0x7bc5492e start_process+0x1d(kernel_start=0x7b8604e0) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2694] in ntdll (0x0032ffe8) 14 0x6803125d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 15 0x6803131b wine_switch_to_stack+0x2a(func=0x7bc54910, arg=0x7b8604e0, stack=0x330000) [/home/julliard/wine/wine/libs/wine/port.c:59] in libwine.so.1 (0xff8613b8) 16 0x7bc5a467 LdrInitializeThunk+0x3a6(kernel_start=<couldn't compute location>, unknown2=<couldn't compute location>, unknown3=<couldn't compute location>, unknown4=<couldn't compute location>) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2750] in ntdll (0xff861428) 17 0x7b866ac0 __wine_kernel_init+0xbbf() [/home/julliard/wine/wine/dlls/kernel32/process.c:1256] in kernel32 (0xff862338) 18 0x7bc5ab33 __wine_process_init+0x182() [/home/julliard/wine/wine/dlls/ntdll/loader.c:2959] in ntdll (0xff8623c8) 19 0x6802eea2 wine_init+0x2a1(argc=0x3, argv=0xff862904, error="", error_size=0x400) [/home/julliard/wine/wine/libs/wine/loader.c:847] in libwine.so.1 (0xff862428) 20 0x7bf00d3b main+0x7a(argc=<is not available>, argv=<is not available>) [/home/julliard/wine/wine/loader/main.c:237] in <wine-loader> (0xff862868) 21 0x682518c5 __libc_start_main+0xf4() in libc.so.6 (0x00000000) 0x686aa077 device_clear_render_targets+0x77 [/home/julliard/wine/wine/dlls/wined3d/device.c:219] in wined3d: movl 0x2c(%edx),%eax 219 || draw_rect->right < target->resource.width -- Alexandre Julliard julliard(a)winehq.org

2 1

Fwd: [GSoC Mentors Announce] Re: GSoC 2013 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching
by Austin English Sept. 23, 2013

Sept. 23, 2013

---------- Forwarded message ---------- From: Carol Smith <carols(a)google.com> Date: Mon, Sep 23, 2013 at 12:04 PM Subject: [GSoC Mentors Announce] Re: GSoC 2013 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching To: GSoC Mentors Announce <gsoc-mentors-announce(a)googlegroups.com> Hi GSoC 2013 mentors and org admins, This is just a friendly reminder that final evaluations are now open and must be submitted by this Friday, 27 September at 19:00 UTC. Don't delay, submit today! Thanks, Carol -- -Austin

1 0

Re: [1/3] winex11: Splitted functions X11DRV_FocusOut (try 2)
by Alexandre Julliard Sept. 23, 2013

Sept. 23, 2013

Sebastian Lackner <sebastian(a)fds-team.de> writes: > - when "virtually" reparenting the plugin window as a child of a > "foreign" window (similar to the systray code) its not possible to get > the focus anymore - the focus code always tries to request the focus for > the WS_POPUP parent, which is a foreign window in this case, and thus > fails. I don't see an easy way to detect/handle if a window is embedded > from user32-code without changing a lot of stuff there - thats why > Pipelight creates the plugin window as a WS_POPUP and makes wine think > it doesn't have any parent (which only has the disadvantage that wine > cannot track the correct window position). I think you really should make it work like the systray and keep track of the hierarchy. You'll run into a lot of hard to fix bugs otherwise. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: add ualapi directory (try 9
by Jacek Caban Sept. 23, 2013

Sept. 23, 2013

Hi Akira, On 09/23/13 10:00, Akira Nakagawa wrote: > From 2ecc71fdb3406d3cf79ebcbd7f6d0c711b68d699 Mon Sep 17 00:00:00 2001 > Message-Id: <2ecc71fdb3406d3cf79ebcbd7f6d0c711b68d699.1379923234.git.matyapiro31(a)gmail…> > From: Akira Nakagawa <matyapiro31(a)gmail.com> > Date: Mon, 23 Sep 2013 17:00:04 +0900 > Subject: [PATCH] add ual directory (try9) > > --- > configure | 2 + > configure.ac | 2 + > dlls/ualapi/Makefile.in | 6 +++ > dlls/ualapi/main.c | 86 +++++++++++++++++++++++++++++++++++++++++ > dlls/ualapi/tests/Makefile.in | 8 ++++ > dlls/ualapi/tests/ualapi_test.c | 38 ++++++++++++++++++ > dlls/ualapi/ualapi.spec | 4 ++ > include/Makefile.in | 1 + > include/ual.h | 48 +++++++++++++++++++++++ > 9 files changed, 195 insertions(+) Please don't include tests in this patch. Tests won't be committed until they are useful, so send them once you have something useful in them and as separated patch. For now, just strip them from the patch. Also, you may consider sending public header (include/ual.h) as a separated patch. And you don't need to include changes to generated files (configure, configure.ac and include/Makefile.in). Cheers, Jacek

1 0

Re: [PATCH 3/5] d3d9/tests: Add a volume V16U16 test.
by Henri Verbeet Sept. 23, 2013

Sept. 23, 2013

On 23 September 2013 13:29, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > Note that Windows drivers disagree on which format they support. Nvidia > has V16U16, AMD supports Q8W8V8U8, at least on r200. I am working on a > more comprehensive converted format test that tests all supported signed > formats with surfaces. Just out of curiosity, do you happen to know if any hardware/driver supports these for render targets?

2 2

Re: [3/4] kernel32/tests: Add 0-length read tests for a pipe.
by Marvin Sept. 23, 2013

Sept. 23, 2013

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2250 Your paranoid android. === wvista (32 bit pipe) === Failure running script in VM: network read error: Resource temporarily unavailable

1 0

Re: add ualapi directory (try 8)
by Marvin Sept. 23, 2013

Sept. 23, 2013

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2311 Your paranoid android. === build (build) === Make failed

1 0

Re: add ualapi directory (try 7)
by Marvin Sept. 23, 2013

Sept. 23, 2013

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2310 Your paranoid android. === build (build) === Make failed

1 0

Re: add ualapi directory (try 5)
by Marvin Sept. 23, 2013

Sept. 23, 2013

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2309 Your paranoid android. === build (build) === Missing build status line The build timed out

1 0

Re: add ualapi directory (try 4)
by Marvin Sept. 23, 2013

Sept. 23, 2013

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2308 Your paranoid android. === build (build) === Make failed

1 0