<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c9">Comment # 9</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 <a class="email" href="mailto:jhnmlkvch9@gmail.com" title="JM9 <jhnmlkvch9@gmail.com>"> JM9</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=94465#c8">comment #8</a>) > (In reply to JM9 from <a href="show_bug.cgi?id=94465#c6">comment #6</a>) > > I was able to run X under valgrind. Here is the log. Let me know if you want > > me to try and build X with -g and try. > > This was just the startup. Hmm, maybe try valgrind > --log-file=/tmp/vg-xorg.txt > The coredumps are consistent with the memcorruption and are just victims of > an earlier bug. So I tried to create the log in /tmp. Still no luck, it only logs the startup not the crash. So then I tried to run valgrind with --trace-children=yes This produces a full log, but when I run X under valgrind with --trace-children=yes option, I can't reproduce the crash anymore! Any idea how I should proceed? While running X under valgrind with this option seems like a workaround for the crash, I'm sure there is a penalty to running X this way all the time. At any rate, I'm attaching the latest log. I hope this contains some clue as to where to look for the problem. Let me know. Thx.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>