1. 05 Jan, 2016 4 commits
  2. 02 Dec, 2015 6 commits
  3. 09 Nov, 2015 3 commits
  4. 08 Nov, 2015 1 commit
  5. 12 Oct, 2015 1 commit
  6. 01 Oct, 2015 2 commits
  7. 30 Jul, 2015 1 commit
  8. 27 May, 2015 2 commits
  9. 19 May, 2015 1 commit
  10. 13 Apr, 2015 5 commits
  11. 28 Mar, 2015 7 commits
  12. 19 Mar, 2015 2 commits
  13. 24 Jan, 2015 2 commits
  14. 21 Jan, 2015 1 commit
    • Kenneth Graunke's avatar
      run: Print which shaders were being processed when crashing. · d8bff3de
      Kenneth Graunke authored
      If the driver hits an assertion failure and aborts, the runner will die,
      which can be hard to debug.  This patch makes the runner catch SIGABRT
      and SIGSEGV and and print out a list of shaders each thread was
      processing before it terminates.
      
       => CRASHED <= while processing these shaders:
      
          shaders/foo/1936.shader_test
          shaders/foo/9991.shader_test
          shaders/foo/1832.shader_test
      
      v2: Handle SIGSEGV too, since SIGABRT doesn't catch real crashes (such
          as null pointer dereferences).  Call _exit() to avoid continuing.
          Use write() in the signal handler since fputs() is not signal safe.
          According to an Austin Group bug tracker entry, strlen() is signal
          safe, so using it should be fine.
      d8bff3de
  15. 20 Jan, 2015 1 commit
  16. 16 Jan, 2015 1 commit