1. 21 May, 2009 1 commit
  2. 12 Mar, 2009 1 commit
  3. 08 Mar, 2009 1 commit
  4. 07 Mar, 2009 2 commits
  5. 06 Mar, 2009 1 commit
  6. 03 Feb, 2009 1 commit
  7. 12 Jan, 2009 1 commit
  8. 11 Jan, 2009 1 commit
  9. 03 Jun, 2008 1 commit
  10. 18 Feb, 2008 1 commit
  11. 04 Feb, 2008 2 commits
  12. 02 Feb, 2008 1 commit
  13. 29 Jan, 2008 3 commits
  14. 05 Sep, 2007 1 commit
  15. 14 Aug, 2007 1 commit
  16. 15 Jun, 2007 1 commit
  17. 27 May, 2007 1 commit
  18. 06 Apr, 2007 2 commits
  19. 30 Mar, 2007 1 commit
  20. 20 Mar, 2007 1 commit
  21. 17 Mar, 2007 1 commit
    • dscho's avatar
      Fix a locking problem in libvncserver · 61cd498f
      dscho authored
      There seems to be a locking problem in libvncserver, with respect to how
      condition variables are used.
      
      On certain machines in our lab, when using a vncviewer to view a display
      that has a very high rate of updates, we will occasionally see the VNC
      server process crash.  In one stack trace that was obtained, an assertion
      had tripped in glibc's pthread_cond_wait, which was called from
      clientOutput.
      
      Inspection of clientOutput suggests that WAIT is being called incorrectly.
      The mutex that protects a condition variable should always be locked when
      calling wait, and on return from the wait will still be locked.  The
      attached patch fixes the locking around this condition variable, and one
      other that I found by grepping the source for similar occurrences.
      Signed-off-by: 's avatarCharles Coffing <ccoffing@novell.com>
      61cd498f
  22. 01 Feb, 2007 1 commit
  23. 31 Jan, 2007 1 commit
  24. 13 Dec, 2006 1 commit
  25. 21 Nov, 2006 1 commit
  26. 13 Nov, 2006 1 commit
  27. 08 Nov, 2006 1 commit
  28. 18 Jul, 2006 1 commit
  29. 12 Jul, 2006 1 commit
  30. 09 Jul, 2006 1 commit
  31. 04 Jul, 2006 1 commit
  32. 08 Jun, 2006 1 commit
  33. 29 May, 2006 1 commit
  34. 16 May, 2006 1 commit
  35. 15 May, 2006 1 commit