Re: 1.4.18

2014-04-19 Thread dormando
Well, that learns me for trying to write software without the 10+ VM buildbots... The i386 one, can you include the output of stats settings, and also manually run: lru_crawler enable (or start with -o lru_crawler) then run stats settings again please? Really weird that it fails there, but not

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote: Well, that learns me for trying to write software without the 10+ VM buildbots... The i386 one, can you include the output of stats settings, and also manually run: lru_crawler enable (or start with -o lru_crawler) then run

Re: 1.4.18

2014-04-19 Thread dormando
On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote: Well, that learns me for trying to write software without the 10+ VM buildbots... The i386 one, can you include the output of stats settings, and also manually run: lru_crawler enable (or start with

Re: 1.4.18

2014-04-19 Thread dormando
Er... reading comprehension fail. I meant 64bit binary still at the bottom there. On Sat, 19 Apr 2014, dormando wrote: On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote: Well, that learns me for trying to write software without the 10+ VM buildbots...

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 1:45 PM, dormando dorma...@rydia.net wrote: On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote: Well, that learns me for trying to write software without the 10+ VM buildbots... The i386 one, can you include the output of stats

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 2:06 PM, Dan McGee dpmc...@gmail.com wrote: On Sat, Apr 19, 2014 at 1:45 PM, dormando dorma...@rydia.net wrote: Any chance you could start the memcached-debug binary under gdb and then crash it the same way? Get a full stack trace. Thinking if I even have a 32bit

Re: 1.4.18

2014-04-19 Thread dormando
On Sat, 19 Apr 2014, Dan McGee wrote: On Sat, Apr 19, 2014 at 1:45 PM, dormando dorma...@rydia.net wrote: On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote:       Well, that learns me for trying to write software without the 10+ VM       buildbots...

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 2:18 PM, dormando dorma...@rydia.net wrote: On Sat, 19 Apr 2014, Dan McGee wrote: On Sat, Apr 19, 2014 at 1:45 PM, dormando dorma...@rydia.net wrote: On Sat, Apr 19, 2014 at 12:43 PM, dormando dorma...@rydia.net wrote: Well, that learns me for

Re: 1.4.18

2014-04-19 Thread dormando
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xf7dbfb40 (LWP 7)] 0xf7f7f988 in __lll_unlock_elision () from /usr/lib/libpthread.so.0 (gdb) bt #0  0xf7f7f988 in __lll_unlock_elision () from /usr/lib/libpthread.so.0 #1 

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 2:45 PM, dormando dorma...@rydia.net wrote: One machine was an i7 with TSX, thus the lock elision segfaults. The other is a much older Core2 machine. Enough differences there to cause problems, especially if we are dealing with threading-type things? Can you give me

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 5:23 PM, dormando dorma...@rydia.net wrote: On Sat, Apr 19, 2014 at 2:45 PM, dormando dorma...@rydia.net wrote: One machine was an i7 with TSX, thus the lock elision segfaults. The other is a much older Core2 machine. Enough differences there to cause

Re: 1.4.18

2014-04-19 Thread Dan McGee
On Sat, Apr 19, 2014 at 6:05 PM, dormando dorma...@rydia.net wrote: Once I wrapped my head around it, figured this one out. This cheap patch fixes the test, although I'm not sure it is the best actual solution. Because we don't set the lru_crawler_running flag on the main thread, but in

Re: 1.4.18

2014-04-19 Thread dormando
On Sat, Apr 19, 2014 at 6:05 PM, dormando dorma...@rydia.net wrote: Once I wrapped my head around it, figured this one out. This cheap patch fixes the test, although I'm not sure it is the best actual solution. Because we don't set the lru_crawler_running flag on the main

Re: Issue 361 in memcached: Segfault in memcached (slabs.c) 1.4.15, patch provided.

2014-04-19 Thread memcached
Updates: Status: Invalid Comment #3 on issue 361 by dorma...@rydia.net: Segfault in memcached (slabs.c) 1.4.15, patch provided. http://code.google.com/p/memcached/issues/detail?id=361 I'm going to close this. *please* let us know if the bug is reproducable under .17 or newer. --

Re: Issue 350 in memcached: memcached: SASL authentication not working in CentOS 6 64-bit

2014-04-19 Thread memcached
Updates: Status: Invalid Comment #3 on issue 350 by dorma...@rydia.net: memcached: SASL authentication not working in CentOS 6 64-bit http://code.google.com/p/memcached/issues/detail?id=350 I don't think you can do that so far as I know :( sorry. -- You received this message because