|
From: Rodrigo D. <ro...@ho...> - 2008-06-19 16:25:50
|
Hi, I am interested in profiling Valgrind's core (using gprof or something similar). I was wondering if anybody had done something similar before. Thank you, Rodrigo |
|
From: Julian S. <js...@ac...> - 2008-06-19 16:36:01
|
On Thursday 19 June 2008 18:25, Rodrigo Dominguez wrote: > Hi, > > I am interested in profiling Valgrind's core (using gprof or something > similar). I was wondering if anybody had done something similar before. Many, many times. But you can't use gprof. Either use OProfile or you can run valgrind-on-valgrind (self hosting) so as to profile it with cachegrind/callgrind. J |
|
From: Rodrigo D. <ro...@ho...> - 2008-06-19 17:03:52
|
Just out of curiosity, what is the problem with gprof? Thanks, Rodrigo > -----Original Message----- > From: Julian Seward [mailto:js...@ac...] > Sent: Thursday, June 19, 2008 12:29 PM > To: val...@li... > Cc: Rodrigo Dominguez > Subject: Re: [Valgrind-developers] Profiling Valgrind's Core > > On Thursday 19 June 2008 18:25, Rodrigo Dominguez wrote: > > Hi, > > > > I am interested in profiling Valgrind's core (using gprof > or something > > similar). I was wondering if anybody had done something > similar before. > > Many, many times. But you can't use gprof. Either use OProfile or > you can run valgrind-on-valgrind (self hosting) so as to profile it > with cachegrind/callgrind. > > J > |
|
From: Konstantin S. <kon...@gm...> - 2008-06-19 20:38:30
|
gprof and many other similar tools require to link something into the profiled application. valgrind won't allow it. tools like Intel PTU (vtssrun) intrude into application's address space. valgrind won't allow it. when using oprofile on x86_64 make sure to build valgrind with -fno-omit-framepointer, otherwise you won't get the callgraph. have fun :) --kcc On Thu, Jun 19, 2008 at 9:03 PM, Rodrigo Dominguez <ro...@ho...> wrote: > Just out of curiosity, what is the problem with gprof? > > Thanks, > > Rodrigo > >> -----Original Message----- >> From: Julian Seward [mailto:js...@ac...] >> Sent: Thursday, June 19, 2008 12:29 PM >> To: val...@li... >> Cc: Rodrigo Dominguez >> Subject: Re: [Valgrind-developers] Profiling Valgrind's Core >> >> On Thursday 19 June 2008 18:25, Rodrigo Dominguez wrote: >> > Hi, >> > >> > I am interested in profiling Valgrind's core (using gprof >> or something >> > similar). I was wondering if anybody had done something >> similar before. >> >> Many, many times. But you can't use gprof. Either use OProfile or >> you can run valgrind-on-valgrind (self hosting) so as to profile it >> with cachegrind/callgrind. >> >> J >> > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Nicholas N. <nj...@cs...> - 2008-06-20 02:37:51
|
On Fri, 20 Jun 2008, Konstantin Serebryany wrote: > gprof and many other similar tools require to link something into the > profiled application. > valgrind won't allow it. > tools like Intel PTU (vtssrun) intrude into application's address space. > valgrind won't allow it. > > when using oprofile on x86_64 make sure to build valgrind with > -fno-omit-framepointer, otherwise you won't get the callgraph. And if you want to use Cachegrind/Callgrind, look at "Self-hosting" in README_DEVELOPERS. Nick |
|
From: Rodrigo D. <ro...@ho...> - 2008-06-21 00:10:21
|
Thank you all for your help. I was able to set up OProfile and I got some numbers. I was wondering if there were any results published (eg. papers) that I can compare mine with. Rodrigo > -----Original Message----- > From: Nicholas Nethercote [mailto:nj...@cs...] > Sent: Thursday, June 19, 2008 10:38 PM > To: Konstantin Serebryany > Cc: Rodrigo Dominguez; > val...@li...; Julian Seward > Subject: Re: [Valgrind-developers] Profiling Valgrind's Core > > On Fri, 20 Jun 2008, Konstantin Serebryany wrote: > > > gprof and many other similar tools require to link > something into the > > profiled application. > > valgrind won't allow it. > > tools like Intel PTU (vtssrun) intrude into application's > address space. > > valgrind won't allow it. > > > > when using oprofile on x86_64 make sure to build valgrind with > > -fno-omit-framepointer, otherwise you won't get the callgraph. > > And if you want to use Cachegrind/Callgrind, look at > "Self-hosting" in > README_DEVELOPERS. > > Nick > |
|
From: Nicholas N. <nj...@cs...> - 2008-06-21 00:16:54
|
On Fri, 20 Jun 2008, Rodrigo Dominguez wrote: > Thank you all for your help. I was able to set up OProfile and I got some > numbers. I was wondering if there were any results published (eg. papers) > that I can compare mine with. See http://www.valgrind.org/docs/pubs.html. The PLDI 2007 paper would be the best starting point. What are you measuring/comparing? Nick |