1. 04 Oct, 2021 - 1 commit
  2. 04 Oct, 2019 - 1 commit
  3. 19 Jun, 2019 - 1 commit
  4. 25 Jan, 2019 - 1 commit
  5. 27 Nov, 2018 - 1 commit
  6. 03 Jul, 2018 - 1 commit
  7. 16 Sep, 2015 - 2 commits
  8. 14 Sep, 2015 - 2 commits
  9. 25 Aug, 2015 - 1 commit
  10. 24 Aug, 2015 - 2 commits
  11. 27 Jul, 2015 - 10 commits
  12. 25 Jun, 2015 - 1 commit
  13. 24 Jun, 2015 - 1 commit
  14. 22 Jun, 2015 - 1 commit
  15. 30 May, 2015 - 1 commit
    • w359405949's avatar
      Update Makefile · 485d0a14
      w359405949 authored
      fix link error while run "make hiredis-example-libuv":
      
      undefined reference to `clock_gettime'
      undefined reference to `clock_getres'
      485d0a14
  16. 03 May, 2015 - 3 commits
  17. 30 Apr, 2015 - 1 commit
    • Alex Balashov's avatar
      Renamed redisContext struct member 'unix' to 'unix_sock' to avoid encountering... · d132d676
      Alex Balashov authored
      Renamed redisContext struct member 'unix' to 'unix_sock' to avoid encountering defined constant 'unix' in GNU C environment (see commit d8145d79).
      
      Not all code using hiredis can compile using '-std=c99', and/or not all users are able to easily make that change to the build process of various open-source projects, so it is more pragmatic to choose a different identifier that does not impose this requirement.
      d132d676
  18. 29 Apr, 2015 - 1 commit
  19. 28 Apr, 2015 - 1 commit
    • antirez's avatar
      Fix memory leak in async spontaneous reply handling · 2fc39eb4
      antirez authored
      When an asynchronous hiredis connection subscribes to a Pub/Sub channel
      and gets an error, and in other related conditions, the function
      redisProcessCallbacks() enters a code path where the link is
      disconnected, however the function returns before freeing the allocated
      reply object. This causes a memory leak. The memory leak was trivial to
      trigger in Redis Sentinel, which uses hiredis, every time we tried to
      subscribe to an instance that required a password, in case the Sentinel
      was configured either with the wrong password or without password at
      all. In this case, the -AUTH error caused the leaking code path to be
      executed.
      2fc39eb4
  20. 16 Apr, 2015 - 7 commits