1. 18 Nov, 2015 1 commit
  2. 13 Jul, 2015 1 commit
  3. 11 Jul, 2015 1 commit
  4. 10 May, 2015 1 commit
  5. 03 Feb, 2015 1 commit
  6. 01 Feb, 2015 1 commit
  7. 13 Aug, 2014 1 commit
  8. 29 Mar, 2014 1 commit
  9. 22 Mar, 2014 2 commits
  10. 14 Nov, 2013 1 commit
  11. 16 Oct, 2013 1 commit
  12. 20 Sep, 2013 1 commit
  13. 16 Sep, 2013 1 commit
  14. 05 Sep, 2013 2 commits
  15. 09 Aug, 2013 1 commit
  16. 05 Jun, 2013 1 commit
  17. 04 Jun, 2013 1 commit
  18. 13 May, 2013 2 commits
  19. 07 May, 2013 1 commit
  20. 02 May, 2013 1 commit
  21. 27 Apr, 2013 1 commit
  22. 10 Mar, 2013 1 commit
  23. 23 Feb, 2013 1 commit
  24. 22 Feb, 2013 1 commit
  25. 14 Dec, 2012 1 commit
  26. 04 Dec, 2012 1 commit
  27. 23 Nov, 2012 1 commit
  28. 25 Oct, 2012 1 commit
  29. 20 Oct, 2012 1 commit
  30. 10 Jul, 2012 1 commit
  31. 02 Jul, 2012 1 commit
  32. 19 Jun, 2012 1 commit
  33. 16 Apr, 2012 1 commit
  34. 10 Apr, 2012 1 commit
    • Martin Storsjö's avatar
      mem: Consistently return NULL for av_malloc(0) · 14f063d2
      Martin Storsjö authored
      Plain POSIX malloc(0) is allowed to return either NULL or a
      non-NULL pointer. The calling code should be ready to handle
      a NULL return as a correct return (instead of a failure) if the size
      to allocate was 0 - this makes sure the condition is handled
      in a consistent way across platforms.
      
      This also avoids calling posix_memalign(&ptr, 32, 0) on OS X,
      which returns an invalid pointer (a non-NULL pointer that causes
      crashes when passed to av_free).
      
      Abort in debug mode, to help track down issues related to
      incorrect handling of this case.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      14f063d2
  35. 28 Jan, 2012 1 commit
  36. 25 Dec, 2011 1 commit
  37. 11 Dec, 2011 1 commit