search

mzhaom / gperftools

Fast, multi-threaded malloc() and nifty performance analysis tools
https://code.google.com/p/gperftools/
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Google perftool crashing #150

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. my kernel is 2.6.28 for X86_64 
2. libunwind and google perf tool are installed with memcached
3. I use the profiling tool for memcached 

What is the expected output? What do you see instead?
When I running memcached under brutis(code.google.com/p/brutis)'s 
benchmark workload and there are about 300 brutis clients to issue get 
requests. The memcached is always crashed. Here is the messages 
from /var/log/messages:
    memcached[17272]: segfault at 42b8b000 ip 00007f760c66c818 sp 
0000000042b890e0 error 4 in libunwind.so.7.0.0[7f760c666000+9000]

When I use the memcached that does not use the perf tool, it is ok.

What version of the product are you using? On what operating system?
libunwind: 0.9.9
  installation: ./configure && make && make install
google perf tool: google-perftools-1.2
  installation: ./configure && make && make install
memcached:
  installation: ./configure LDFLAGS="-L/opt/memcached/lib -
L/usr/local/lib" LIBS=-lprofiler CPPFLAGS=-I/opt/memcached/include --
prefix=/opt/memcached --exec-prefix=/opt/memcached --with-
libevent=/opt/memcached --enable-64bit

Original issue reported on code.google.com by mingfan...@gmail.com on 24 Jun 2009 at 2:29

GoogleCodeExporter commented 9 years ago

Original comment by `` on 18 Jan 2012 at 9:37

GoogleCodeExporter commented 9 years ago 
my memcached version is 1.3.3
and I am using this instruction to start the profiling:
CPUPROFILE=/tmp/prof.out /opt/memcached/bin/memcached -u nobody-p 11000 -m 
2048 -c 3096 -t 8 -d

Original comment by mingfan...@gmail.com on 24 Jun 2009 at 2:35

GoogleCodeExporter commented 9 years ago 
Unfortunately perftools on x86_64 still has known issues with libtool.  What 
happens
when you try to compile perftools with the --enable-frame-pointer option 
instead of
trying to use libunwind?

Original comment by csilv...@gmail.com on 24 Jun 2009 at 3:09

GoogleCodeExporter commented 9 years ago 
Oops, sorry for the typo: I meant 'libunwind' above, not 'libtool'.

Original comment by csilv...@gmail.com on 24 Jun 2009 at 3:27

GoogleCodeExporter commented 9 years ago 
It seems that the method using --enable-frame-pointer works well for me. thanks 
a lot

Original comment by mingfan...@gmail.com on 24 Jun 2009 at 4:54

GoogleCodeExporter commented 9 years ago

Original comment by csilv...@gmail.com on 24 Jun 2009 at 5:08