<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Xorg crashes in VT switch"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=94465#c11">Comment # 11</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Xorg crashes in VT switch"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=94465">bug 94465</a>
              from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
        <pre>(In reply to JM9 from <a href="show_bug.cgi?id=94465#c10">comment #10</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=122260" name="attach_122260" title="X under valgrind trace-children">attachment 122260</a> <a href="attachment.cgi?id=122260&action=edit" title="X under valgrind trace-children">[details]</a></span>
> X under valgrind trace-children

> log for running X as follows:

> exec valgrind --trace-children=yes --log-file=/tmp/vg-xorg.txt /usr/bin/X.bak</span >

Darn, that was with xf86-video-intel not built for valgrind so valgrind doesn't
understand the allocations/usage of video memory. Can you please build
xf86-video-intel with ./configure --enable-debug --enable-valgrind ?

Even if it does not crash with valgrind, valgrind probably detected the error.
Probably. (There are a number of causes (from using the GPU) that valgrind
could not and simply changing the timing would be enough.) But since this
sounds i-v-o related, I expect valgrinid to catch the error.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>