1. 06 Oct, 2006 1 commit
  2. 03 Oct, 2006 4 commits
  3. 22 Sep, 2006 2 commits
  4. 21 Sep, 2006 1 commit
  5. 15 Sep, 2006 4 commits
  6. 14 Sep, 2006 1 commit
  7. 13 Sep, 2006 3 commits
  8. 12 Sep, 2006 6 commits
  9. 11 Sep, 2006 2 commits
  10. 09 Sep, 2006 1 commit
  11. 07 Sep, 2006 1 commit
    • Eric Wong's avatar
      utils.c: fix xrealloc · f5c7f3da
      Eric Wong authored
      (based on suggested patch by Jan-Benedict Glaw):
      > While hacking mpd, I noticed that an assert()ion in xrealloc is wrong.
      > A null size is perfectly legal, so we shouldn't assert on that.
      
      Since some C libraries return NULL when size == 0, we'll make
      sure we get a free()-able pointer since some of those C
      libraries also barf on free(NULL).
      
      git-svn-id: https://svn.musicpd.org/mpd/trunk@4740 09075e82-0dd4-0310-85a5-a0d7c8717e4f
      f5c7f3da
  12. 06 Sep, 2006 3 commits
  13. 30 Aug, 2006 1 commit
  14. 28 Aug, 2006 9 commits
  15. 26 Aug, 2006 1 commit
    • Eric Wong's avatar
      Replace strdup and {c,re,m}alloc with x* variants to check for OOM errors · 90847fc8
      Eric Wong authored
      I'm checking for zero-size allocations and assert()-ing them,
      so we can more easily get backtraces and debug problems, but we'll
      also allow -DNDEBUG people to live on the edge if they wish.
      
      We do not rely on errno when checking for OOM errors because
      some implementations of malloc do not set it, and malloc
      is commonly overridden by userspace wrappers.
      
      I've spent some time looking through the source and didn't find any
      obvious places where we would explicitly allocate 0 bytes, so we
      shouldn't trip any of those assertions.
      
      We also avoid allocating zero bytes because C libraries don't
      handle this consistently (some return NULL, some not); and it's
      dangerous either way.
      
      git-svn-id: https://svn.musicpd.org/mpd/trunk@4690 09075e82-0dd4-0310-85a5-a0d7c8717e4f
      90847fc8