<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - intel-virtual-overlay: only background image and mouse cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=68987#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - intel-virtual-overlay: only background image and mouse cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=68987">bug 68987</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>My suspicion is that I've forgotten my X and missed a flag somewhere... If you apply diff --git a/tools/virtual.c b/tools/virtual.c index 8e241e5..ee8b3c6 100644 --- a/tools/virtual.c +++ b/tools/virtual.c @@ -56,7 +56,7 @@ #include <fcntl.h> #include <assert.h> -#if 0 +#if 1 #define DBG(x) printf x #else #define DBG(x) you will get lots of debug output if you then use: intel-virtual-output -f > i-v-o.txt and then repeat the test of dragging the window onto the virtual screen. What I am looking for in the i-v-o.txt is whether we are detecting and then painting the damaged regions on the virtual screen.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>