New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redis crush #1221
Comments
Thanks for reporting, please could you specify an example of script that triggers this issue? |
Here's what i get with GDB: Program received signal SIGSEGV, Segmentation fault. |
Hello, thanks. What is the way you use the file "ban" attached to your file? At a first glance it does not seem to be properly formatted as as the end it misses the final quote character. Please could you provide a very small program reproducing the issue? Thank you. |
Not needed, sorry, I'm now able to reproduce it, I forgot to attach the slave when simulating the large MSET thing. Thanks for reporting. |
Fixed, I'll close the issue after regression tests are implemented. |
Sorry for the final quote, just forgot it. Here's link to gdb core file: https://docs.google.com/file/d/0B6nhA34lmPYJUElXT2E5bTMxQ0U/edit?usp=sharing |
@s-tchaikovsky thanks, the latest version of Redis 2.8 and unstable are now fixed, however I'll release a proper 2.8 release candidate 2 version in the next days. Closing the issue now that there is a regression test. Thanks for your help. |
Running version 2.8.0-rc1 on Ubunut 12.04
Getting following error while setting about 100 values with MSET command
*** stack smashing detected ***: ./redis-server *:6379 terminated
[2726] 26 Jul 15:00:44.137 #
=== REDIS BUG REPORT START: Cut & paste starting from here ===
[2726] 26 Jul 15:00:44.140 # Redis 2.7.101 crashed by signal: 11
[2726] 26 Jul 15:00:44.141 # Failed assertion: (:0)
[2726] 26 Jul 15:00:44.142 # --- STACK TRACE
Segmentation fault (core dumped)
Tried that on different servers and virtual machine. 100% reproduction
Upd:
Here's link to script i'm trying to execute
https://docs.google.com/file/d/0B6nhA34lmPYJbUlRVjJiWmxHelk/edit?usp=sharing
The text was updated successfully, but these errors were encountered: