1. 14 May, 2018 1 commit
  2. 10 May, 2018 1 commit
  3. 09 May, 2018 1 commit
  4. 06 Jan, 2018 2 commits
  5. 05 Jan, 2018 5 commits
  6. 28 Dec, 2017 1 commit
    • Dmitri Vorobiev's avatar
      Strip compiler options from the CC variable · 12a9d1a3
      Dmitri Vorobiev authored
      
      
      The Makefile checks validity of the compiler command in the CC
      variable by feeding the contents of that variable to the `type'
      utility. Some environments include compiler options in the CC
      variable such as architecture specific tuning flags. For such
      cases it is necessary to first strip everything except the
      command itself from the contents of the CC variable prior to
      checking the command with the type utility, which is what this
      patch is introducing. We use shell parameter expansion mechanism
      for this purpose.
      Signed-off-by: default avatarDmitri Vorobiev <dmitri.vorobiev@movial.com>
      12a9d1a3
  7. 27 Dec, 2017 1 commit
    • Dmitri Vorobiev's avatar
      Remove $(ARCH) expansion from the Makefile · 3238cf4f
      Dmitri Vorobiev authored
      
      
      Some compilation environments (such as Yocto) define the ARCH
      environment variable to indicate the target architecture. For
      such enviroments, hiredis build fails, because the expanded
      $(ARCH) variable in the Makefile gets erroneously interpreted
      as an argument to the `-ggdb' command line option during the
      compilation stage or as an input file name during the linking
      stage.
      
      This patch removes $(ARCH) expansions from the Makefile. This
      doesn't harm cross-compilation, the latter goes fine with the
      properly assigned CC environment variable. For native builds,
      this patch does not imply any changes.
      Signed-off-by: default avatarDmitri Vorobiev <dmitri.vorobiev@movial.com>
      3238cf4f
  8. 29 Nov, 2017 1 commit
  9. 07 Nov, 2017 2 commits
  10. 30 Oct, 2017 1 commit
  11. 01 Sep, 2017 2 commits
  12. 15 Jul, 2017 3 commits
    • not-a-robot[bot]'s avatar
      Merge #533 · 97d611e9
      not-a-robot[bot] authored
      533: Small fixes r=badboy
      
      97d611e9
    • not-a-robot[bot]'s avatar
      Merge #524 #525 · 74be165c
      not-a-robot[bot] authored
      524: Don't pass a negative value to __redisAsyncCommand if redisFormatSdsCommandArgv fails r=badboy
      
      
      
      525: Fix compilation on FreeBSD 10.3 with default compiler r=badboy
      
      Given FreeBSD 10.3 with default compiler:
      
      > $ cc -v
      > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
      > Target: x86_64-unknown-freebsd10.3
      
      Defining _XOPEN_SOURCE to 600 on the fixed line leads to the following errors:
      
      > cc -std=c99 -pedantic -c -O3 -fPIC  -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb  net.c
      > net.c:435:29: error: use of undeclared identifier 'AF_LOCAL'
      >     if (redisCreateSocket(c,AF_LOCAL) < 0)
      >                             ^
      > net.c:460:21: error: use of undeclared identifier 'AF_LOCAL'
      >     sa.sun_family = AF_LOCAL;
      >                     ^
      > 2 errors generated.
      > 
      
      AF_LOCAL is defined in sys/socket.h within ifdef __BSD_VISIBLE.
      
      __BSD_VISIBLE could be defined in sys/cdefs.h, but it is never done if _XOPEN_SOURCE is defined.
      
      So on FreeBSD _XOPEN_SOURCE shouldn't be defined.
      74be165c
    • not-a-robot[bot]'s avatar
      Merge #523 · 7d996522
      not-a-robot[bot] authored
      523: Fix leak if setsockopt fails r=badboy
      
      7d996522
  13. 16 Jun, 2017 1 commit
  14. 15 Jun, 2017 2 commits
  15. 17 May, 2017 1 commit
  16. 15 May, 2017 2 commits
  17. 07 Apr, 2017 4 commits
  18. 28 Mar, 2017 1 commit
    • zfz's avatar
      Update libevent.h · 515228e5
      zfz authored
      event_del can not free the "e->rev" and "e->wev",that will leak when reconnect the redis
      515228e5
  19. 22 Mar, 2017 2 commits
  20. 30 Jan, 2017 2 commits
  21. 23 Jan, 2017 1 commit
  22. 30 Dec, 2016 1 commit
  23. 09 Dec, 2016 2 commits
    • not-a-robot's avatar
      Auto merge of #429 - xinchuantao:master, r=badboy · 33152ad1
      not-a-robot authored
      using new version libevent
      33152ad1
    • not-a-robot's avatar
      Auto merge of #468 - paul-scott:master, r=badboy · b4f9fc1a
      not-a-robot authored
      Prevented uv adapter from calling write when context has been freed
      
      The `redisLibuvPoll` function can be called with both the `UV_READABLE` and `UV_WRITABLE` flags set at the same time.  Calling `redisAsyncHandleRead` can lead to a disconnect and the context being cleaned up/freed.  If this happens then `redisAsyncHandleWrite` should not be called otherwise memory read/write errors and duplicate freeing will occur.
      
      These changes prevent this from happening by having the `redisLibuvCleanup` callback indicate that the context has been cleaned.  This is done indirectly by setting the context to a null pointer, maybe someone can come up with a cleaner way.
      b4f9fc1a