Hrm, I think I answered too quickly. I use that directly with valgrind
launching the daemon, not through vstart. Not sure if it passes it
through properly. Maybe try Sage's suggestion or see if valgrind works
when you launch the daemon directly?
Mark
On 07/11/2013 01:21 AM, Ranjan Sarpangala Venkatesh wrote:
Hi Mark,
I upgraded valgrind to 3.8.1 and also used
--soname-synonyms=somalloc=*tcmalloc* option. However, no massif.out
file was created.
Kindly let me know if i am missing something.
With regards
Ranjan
On Tue, Jul 9, 2013 at 6:15 PM, Mark Nelson <mark.nelson@xxxxxxxxxxx> wrote:
Hi,
I ran into this problem a while back and it was because I was trying to use
a version of valgrind that didn't support tcmalloc (which Ceph was compiled
to use). Try upgrading valgrind to 3.8.0 or newer. You'll also need to
pass something like:
--soname-synonyms=somalloc=*tcmalloc*
Mark
On 07/09/2013 08:10 PM, Ranjan Sarpangala Venkatesh wrote:
Hi,
I am trying to collect memory of the OSD daemon with the following
./vstart.sh -n -x -l --valgrind_osd 'massif'
However, when I print massif.out file there is nothing
cat massif.out.15391
desc: (none)
cmd: ./ceph-osd -i 0 -c ceph.conf -f
time_unit: i
#-----------
snapshot=0
#-----------
time=0
mem_heap_B=0
mem_heap_extra_B=0
mem_stacks_B=0
heap_tree=empty
--
With regards,
Ranjan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
