Comment #2 on issue 370 by [email protected]: memcached(v1.4.15) dead
loop bug.
http://code.google.com/p/memcached/issues/detail?id=370
i can't reproduce even in 1.4.15, and i watch the memcached's github and
review every commit,i don't think it is fixed. also, i don't think this
is the same bug as the alloc segfault. if it->h_next is 0 or other random
value, it maybe a memory fault; but now it->h_next point to itself, it is
likely a logical error when hash expanding. i will try to modify the hash
expanding code to reproduce the bug more easier..
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
