Jdesk / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

memcached 1.4.4 segfaults error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit #117

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. ./configure --prefix= --exec-prefix=/usr --datarootdir=/usr/share (note not 
with 64 
enable)
2. run "./memcached-debug -vvv -u nobody"
3. connect with telnet on port 11211

What is the expected output? What do you see instead?

memcached segfaults on first connect attempt instead of displaying the telnet 
session

in /var/log/messages

kernel: memcached-debug[9024]: segfault at 0000000000000000 rip 
0000000000400012 rsp 
00007fff93258c08 error 6

What version of the product are you using? On what operating system?
Running memcached 1.4.4 on 64bit CentOS 5.4 2.6.18 kernel

Please provide any additional information below.
The debug output when connecting with telnet;

slab class  37: chunk size    315872 perslab       3
slab class  38: chunk size    394840 perslab       2
slab class  39: chunk size    493552 perslab       2
slab class  40: chunk size    616944 perslab       1
slab class  41: chunk size    771184 perslab       1
slab class  42: chunk size   1048576 perslab       1
<26 server listening (auto-negotiate)
<27 send buffer was 129024, now 268435456
Segmentation fault

Original issue reported on code.google.com by tacoham...@gmail.com on 23 Dec 2009 at 1:59

GoogleCodeExporter commented 9 years ago
This also occurs on RedHat ES5 (which makes sense since CentOS is based on 
RedHat ES).

Kernel version: 2.6.18-92.1.6.el5xen #1 SMP

This only occurs for me when the compile occurs on a 64-bit CPU.  If I compile 
it on a 
32-bit machine, the binary produced works just fine on both 64-bit and 32-bit 
machines.  
But a 64-bit binary runs on neither CPU.

Original comment by brandon....@gmail.com on 23 Dec 2009 at 6:56

GoogleCodeExporter commented 9 years ago
I didn't manage to get a coredump, but using backtrace in gdb i got this output;

(gdb) bt
#0  0x0000000000400012 in ?? ()
#1  0x00000035d2e03c15 in event_base_loop () from /usr/lib64/libevent-1.1a.so.1
#2  0x000000000040736b in main (argc=<value optimized out>, argv=<value 
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.

Original comment by tacoham...@gmail.com on 30 Dec 2009 at 9:11

GoogleCodeExporter commented 9 years ago
Is that actually libevent 1.1a?  That's a few days short of five years old.

Original comment by dsalli...@gmail.com on 30 Dec 2009 at 9:52

GoogleCodeExporter commented 9 years ago
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!

Original comment by tacoham...@gmail.com on 30 Dec 2009 at 10:46

GoogleCodeExporter commented 9 years ago

Original comment by trond.no...@gmail.com on 30 Dec 2009 at 11:24