Updates:
Status: WontFix
Comment #2 on issue 179 by trond.no...@gmail.com: Solaris 10 compilation
fails
http://code.google.com/p/memcached/issues/detail?id=179
configure checks for the tcov binary during configure, and tries to add
coverage support if you've got it installed. You
Status: Accepted
Owner: trond.no...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 210 by trond.no...@gmail.com: code coverage should not be enabled
by default...
http://code.google.com/p/memcached/issues/detail?id=210
Currently we've got --disable-coverage.. This should be flipped
Updates:
Status: Invalid
Comment #1 on issue 210 by trond.no...@gmail.com: code coverage should not
be enabled by default...
http://code.google.com/p/memcached/issues/detail?id=210
This is already fixed in 1.6...
Comment #16 on issue 99 by thomc...@gmail.com: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
Hi,
Thank you for checking in, and yes, I am still watching this ticket as it
still continues to be an issue for me. I manually apply my patch
Updates:
Status: Fixed
Comment #2 on issue 144 by trond.no...@gmail.com: ETIME 62 error under
OpenSolaris while receiving big data
http://code.google.com/p/memcached/issues/detail?id=144
I just built 1.4.6-rc1 on oi_148 in 32 and 64 bit mode with libevent 2.0.12
and make test
dmesg, gdb and output could help
2011/7/13 memcac...@googlecode.com:
Comment #16 on issue 99 by thomc...@gmail.com: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
Hi,
Thank you for checking in, and yes, I am still watching this ticket as
Comment #2 on issue 199 by windw...@gmx.com: Memcached compilation fails
with GCC 4.6.0
http://code.google.com/p/memcached/issues/detail?id=199
I can confirm that this is fixed in 1.4.6-rc1.
Just compiled it with gcc 4.6.1 and it works fine without
using -Wno-error=unused-but-set-variable.
Comment #2 on issue 200 by windw...@gmx.com: DTrace integration fails with
GCC 4.6.0 on Solaris x86
http://code.google.com/p/memcached/issues/detail?id=200
Update:
Verified the issue with memcached 1.4.6-rc1 and gcc 4.6.1. Compilation with
gcc 4.5.3 works fine. Setting optimization to O1
Updates:
Status: Fixed
Comment #8 on issue 127 by dorma...@rydia.net: incr/decr operations are not
thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
trying to close this again.
Comment #18 on issue 99 by dorma...@rydia.net: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
Also, can you try the 1.6 beta and see if that fails for you?
Comment #19 on issue 99 by thomc...@gmail.com: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
Yes, I am still running this on gentoo, PHP 5.3.3 with a memcache 2.2.5
client (as reported by phpinfo()). Here is a backtrace under gdb:
gdb
Comment #20 on issue 99 by thomc...@gmail.com: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
Hi,
As for testing 1.6.0-beta, I am having trouble manually
generating configure since it is missing in the source (as it was in the
release
Comment #21 on issue 99 by dorma...@rydia.net: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
http://memcached.googlecode.com/files/memcached-1.6.0_beta1.tar.gz - are
you *sure* that you're using this file? The configure script is certainly
Comment #22 on issue 99 by thomc...@gmail.com: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
I was definitely *not* using that file :) Downloaded it from the github
source link. With the provided tar link, I am getting the following
Comment #23 on issue 99 by dorma...@rydia.net: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
I have relative little clue on what's been changed in 1.6 :P Was mostly
curious if it'd been fixed there.
I'm still nervous about the change
Comment #2 on issue 169 by jonat...@gmail.com: probably incorrect treatment
of negative expiration time
http://code.google.com/p/memcached/issues/detail?id=169
For me, using a value of -60 in a cas seemed to always expire immediately,
but I probably never did it within 60 seconds of
Comment #7 on issue 121 by trond.no...@gmail.com: Values with certain keys
are not stored on solaris sparc with libevent 1.4.3
http://code.google.com/p/memcached/issues/detail?id=121
Added missing runtime path. Fixed in
Comment #3 on issue 200 by trond.no...@gmail.com: DTrace integration fails
with GCC 4.6.0 on Solaris x86
http://code.google.com/p/memcached/issues/detail?id=200
I'd appreciate a gcc 4.6.1 for solaris 10 x86.. It would be easier for me
to build and play around with disassembly if I can
Hey,
http://code.google.com/p/memcached/wiki/NewDevelopmentProcess
^ I've updated this page to hopefully reflect reality now.
Since it's taking so long to stabilize the 1.6 tree, I've decided to
revive the 1.4 tree.
We will begin again to make regular releases of 1.4 and 1.6 will track on
its
19 matches
Mail list logo
