I am confused - once upon a time, there would have been only a sysmem surface on the wined3d side, and wined3d does the clear directly on its system memory and reads the data from the source's system memory in the Blt() call.
Nowadays we have a video memory draw texture for sysmem surfaces because one can use them for texturing on native ddraw.
Is the issue here that ddraw accidentally made wined3d perform stuff on the vidmem draw texture rather than the 'original' system wiend3d_texture?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4781#note_56670
This mainly allows Wine to reset the tty settings upon
termination and not let gdb do it (cf bug report).
Change: user is now required to explicitely terminate gdb
('quit' command) upon debuggee termination.
Wine-Bugs: https://bugs.winehq.org/show_bug.cgi?id=56032
Signed-off-by: Eric Pouech <epouech(a)codeweavers.com>
--
v2: winedbg: Wait for gdb to terminate before exiting (proxy mode).
https://gitlab.winehq.org/wine/wine/-/merge_requests/4776