- 18 Sep, 2019 1 commit
-
-
antirez authored
-
- 31 Aug, 2019 1 commit
-
-
zhudacai 00228490 authored
of aarch64. The content comes from the definition of the sigcontext and tested on my aarch64 server. sigcontext defined at the linux kernel code: arch/arm64/include/uapi/asm/sigcontext.h
-
- 24 Jul, 2019 1 commit
-
-
Oran Agra authored
this implements #6012
-
- 03 Jul, 2019 1 commit
-
-
antirez authored
-
- 02 Jun, 2019 1 commit
-
-
Oran Agra authored
jemalloc 5 doesn't immediately release memory back to the OS, instead there's a decaying mechanism, which doesn't work when there's no traffic (no allocations). this is most evident if there's no traffic after flushdb, the RSS will remain high. 1) enable jemalloc background purging 2) explicitly purge in flushdb
-
- 11 Feb, 2019 1 commit
-
-
Chris Lamb authored
__x86_64__ is defined on the on the x32 architecture and the conditionals in debug.c therefore assume the size of (void*) etc: debug.c: In function 'getMcontextEip': debug.c:757:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] return (void*) uc->uc_mcontext.gregs[16]; /* Linux 64 */ ^ debug.c: In function 'logRegisters': debug.c:920:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] logStackContent((void**)uc->uc_mcontext.gregs[15]); We can remedy this by checking for __ILP32__ first. See: https://wiki.debian.org/ArchitectureSpecificsMemo ... for more info.
-
- 09 Jan, 2019 7 commits
- 11 Dec, 2018 1 commit
-
-
antirez authored
Verified to be able to trigger at least #5632. Does not report other issues.
-
- 07 Dec, 2018 2 commits
- 30 Nov, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 25 Nov, 2018 2 commits
-
-
David Carlier authored
Special treatment here as backtrace support is optional, cannot be found via pkg-config and similar neither.
-
David Carlier authored
FreeBSD/DragonFlyBSD does have backtrace only it does not belong to libc.
-
- 08 Nov, 2018 1 commit
-
-
David Carlier authored
-
- 09 Oct, 2018 1 commit
-
-
antirez authored
Related to #4804.
-
- 30 Jul, 2018 1 commit
-
-
Oran Agra authored
-
- 02 Jul, 2018 1 commit
-
-
antirez authored
-
- 28 Jun, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 18 Jun, 2018 1 commit
-
-
antirez authored
-
- 09 Jun, 2018 1 commit
-
-
Itamar Haber authored
-
- 08 Jun, 2018 1 commit
-
-
antirez authored
-
- 07 Jun, 2018 1 commit
-
-
Itamar Haber authored
-
- 02 Jun, 2018 1 commit
-
-
WuYunlong authored
and will not be inconsistent after we call debug loadaof. Before this commit, there were 2 problems: 1, When appendonly is set to no and there is not a appendonly file, redis-server will crash if we call DEBUG LOADAOF. 2, When appendonly is set to no and there is a appendonly file, redis-server will hold different data after loading appendonly file.
-
- 25 May, 2018 1 commit
-
-
Mota authored
-
- 29 Mar, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 09 Jan, 2018 1 commit
-
-
gnuhpc authored
-
- 06 Dec, 2017 1 commit
-
-
antirez authored
The main change introduced by this commit is pretending that help arrays are more text than code, thus indenting them at level 0. This improves readability, and is an old practice when defining arrays of C strings describing text. Additionally a few useless return statements are removed, and the HELP subcommand capitalized when printed to the user.
-
- 04 Dec, 2017 2 commits
-
-
zhaozhao.zz authored
-
antirez authored
With PSYNC2 to force a full SYNC in tests is hard. With this new DEBUG subcommand we just need to call it and then CLIENT KILL TYPE master in the slave.
-
- 01 Dec, 2017 1 commit
-
-
antirez authored
-
- 28 Nov, 2017 2 commits
-
-
Itamar Haber authored
This adds a new `addReplyHelp` helper that's used by commands when returning a help text. The following commands have been touched: DEBUG, OBJECT, COMMAND, PUBSUB, SCRIPT and SLOWLOG. WIP Fix entry command table entry for OBJECT for HELP option. After #4472 the command may have just 2 arguments. Improve OBJECT HELP descriptions. See #4472. WIP 2 WIP 3
-
Itamar Haber authored
-
- 20 Sep, 2017 1 commit
-
-
zhaozhao.zz authored
This commit is a reinforcement of commit c1c99e9f. 1. Replication information can be stored when the RDB file is generated by a mater using server.slaveseldb when server.repl_backlog is not NULL, or set repl_stream_db be -1. That's safe, because NULL server.repl_backlog will trigger full synchronization, then master will send SELECT command to replicaiton stream. 2. Only do rdbSave* when rsiptr is not NULL, if we do rdbSave* without rdbSaveInfo, slave will miss repl-stream-db. 3. Save the replication informations also in the case of SAVE command, FLUSHALL command and DEBUG reload.
-
- 06 Jul, 2017 1 commit
-
-
antirez authored
-