All of lore.kernel.org
 help / color / mirror / Atom feed
* Using valgrind_osd option
@ 2013-07-10  1:10 Ranjan Sarpangala Venkatesh
  2013-07-10  1:15 ` Mark Nelson
  0 siblings, 1 reply; 6+ messages in thread
From: Ranjan Sarpangala Venkatesh @ 2013-07-10  1:10 UTC (permalink / raw)
  To: ceph-devel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Using valgrind_osd option
  2013-07-10  1:10 Using valgrind_osd option Ranjan Sarpangala Venkatesh
@ 2013-07-10  1:15 ` Mark Nelson
  2013-07-11  6:21   ` Ranjan Sarpangala Venkatesh
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Nelson @ 2013-07-10  1:15 UTC (permalink / raw)
  To: Ranjan Sarpangala Venkatesh; +Cc: ceph-devel

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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Using valgrind_osd option
  2013-07-10  1:15 ` Mark Nelson
@ 2013-07-11  6:21   ` Ranjan Sarpangala Venkatesh
  2013-07-11 19:38     ` Sage Weil
  2013-07-11 20:21     ` Mark Nelson
  0 siblings, 2 replies; 6+ messages in thread
From: Ranjan Sarpangala Venkatesh @ 2013-07-11  6:21 UTC (permalink / raw)
  To: Mark Nelson; +Cc: ceph-devel

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@inktank.com> 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@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>



-- 
With regards,
Ranjan

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Using valgrind_osd option
  2013-07-11  6:21   ` Ranjan Sarpangala Venkatesh
@ 2013-07-11 19:38     ` Sage Weil
  2013-07-11 20:21     ` Mark Nelson
  1 sibling, 0 replies; 6+ messages in thread
From: Sage Weil @ 2013-07-11 19:38 UTC (permalink / raw)
  To: Ranjan Sarpangala Venkatesh; +Cc: Mark Nelson, ceph-devel

On Wed, 10 Jul 2013, 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.

I haven't run into this.  I usually run without tcmalloc in my dev 
environment so that I can do valgrind leak checking, though.  
make clean and ./do_autogen.sh -d 3 -T in the base dir of ceph.git...?

sage



> 
> With regards
> Ranjan
> 
> On Tue, Jul 9, 2013 at 6:15 PM, Mark Nelson <mark.nelson@inktank.com> 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@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>
> >
> 
> 
> 
> -- 
> With regards,
> Ranjan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Using valgrind_osd option
  2013-07-11  6:21   ` Ranjan Sarpangala Venkatesh
  2013-07-11 19:38     ` Sage Weil
@ 2013-07-11 20:21     ` Mark Nelson
  2013-07-12  6:45       ` Ranjan Sarpangala Venkatesh
  1 sibling, 1 reply; 6+ messages in thread
From: Mark Nelson @ 2013-07-11 20:21 UTC (permalink / raw)
  To: Ranjan Sarpangala Venkatesh; +Cc: ceph-devel

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@inktank.com> 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@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>
>
>


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Using valgrind_osd option
  2013-07-11 20:21     ` Mark Nelson
@ 2013-07-12  6:45       ` Ranjan Sarpangala Venkatesh
  0 siblings, 0 replies; 6+ messages in thread
From: Ranjan Sarpangala Venkatesh @ 2013-07-12  6:45 UTC (permalink / raw)
  To: Mark Nelson; +Cc: ceph-devel

Hi Sage,Mike

I reverted back to valgrind version 3.7.0, did what Sage suggested and
it worked. However, with valgrind 3.8.1 no massif.out file was created
even while running a build with no tcmalloc. Not sure why this is
happening.

Thanks Sage and Mark for your help.

With regards
Ranjan

On Thu, Jul 11, 2013 at 1:21 PM, Mark Nelson <mark.nelson@inktank.com> wrote:
> 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@inktank.com>
>> 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@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>
>>
>>
>



-- 
With regards,
Ranjan

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-07-12  6:45 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-10  1:10 Using valgrind_osd option Ranjan Sarpangala Venkatesh
2013-07-10  1:15 ` Mark Nelson
2013-07-11  6:21   ` Ranjan Sarpangala Venkatesh
2013-07-11 19:38     ` Sage Weil
2013-07-11 20:21     ` Mark Nelson
2013-07-12  6:45       ` Ranjan Sarpangala Venkatesh

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.