Re: Issue 118 in memcached: Bad parameter -pthread being used on Solaris (instead of -pthreads)
Comment #1 on issue 118 by trond.norbye: Bad parameter -pthread being used on Solaris (instead of -pthreads) http://code.google.com/p/memcached/issues/detail?id=118 According to http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html both -pthread and -pthreads should work on SPARC. What is the gcc-version you are using? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Issue 118 in memcached: Bad parameter -pthread being used on Solaris (instead of -pthreads)
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 118 by aavakian: Bad parameter -pthread being used on Solaris (instead of -pthreads) http://code.google.com/p/memcached/issues/detail?id=118 What steps will reproduce the problem? 1. On SunOS (see below for my particular version), installed libevent-1.4.13: cd libevent-1.4.13-stable/ ./configure make make install 2. Configure and make memcached: cd memcached-1.4.4/ ./configure --with-libevent=/root/libevent-1.4.13-stable make 3. Notice the warnings about -pthread: gcc: unrecognized option `-pthread' The first time I compiled it, I did not notice this problem in make, and I installed anyways. The result was that I could not reliably cache any value > 7K. At 7+K the cache would start failing. To fix it, I edited memcached-1.4.4/configure and changed -pthread to -pthreads (plural for SunOS). That worked, and fixed my max value for cache size to 1MB as it should be. I believe this is a problem in ./configure for memcached. Thanks, -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Re: Dump Cache
> Dumping Cache is a feature that is discussed in details. I agree that > dumping cache to keep it warm may not be the best idea. However, I > recently got into the situation where we lost the database and we lost > the backup of the database. So, the only thing we had was running > memcached (please stop laughing, it's only a little funny)... So I had > to dump the content of memcached to attempt to recreate the data > > I used the tool described here: > http://lists.danga.com/pipermail/memcached/2007-April/003905.html > > But the dump was painful as I had to dump chunks and then delete them > from memcached so that I can dump other chunks. > > Is the feature to dump cache still being considered? Future storage engines might support it... but people should try really, really, really hard to never need it.
Re: Issue 117 in memcached: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
Updates: Status: Invalid Comment #5 on issue 117 by trond.norbye: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit http://code.google.com/p/memcached/issues/detail?id=117 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Re: Issue 117 in memcached: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
Comment #4 on issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit http://code.google.com/p/memcached/issues/detail?id=117 I feel stupid for running CentOS 5.4 someone tell me WHY? This bug is resolved by installing libevent-devel-1.3b-1.el5.test.x86_64.rpm and libevent-1.3b- 1.el5.test.x86_64.rpm on CentOS 5.4 Thanks for pointing this silly "bug" out, this case is solved! -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Re: Issue 117 in memcached: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
Comment #3 on issue 117 by dsallings: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit http://code.google.com/p/memcached/issues/detail?id=117 Is that actually libevent 1.1a? That's a few days short of five years old. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Re: Issue 117 in memcached: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
Comment #2 on issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit http://code.google.com/p/memcached/issues/detail?id=117 I didn't manage to get a coredump, but using backtrace in gdb i got this output; (gdb) bt #0 0x00400012 in ?? () #1 0x0035d2e03c15 in event_base_loop () from /usr/lib64/libevent-1.1a.so.1 #2 0x0040736b in main (argc=, argv=optimized out>) at memcached.c:4680 I hope this information is useful, please let me know if there is more action from my part required. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
