|
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 > |