Re: [Valgrind-users] using valgrind at specific point while running program

[Mahmood N. <nt_...@ya...>]

>What particular tool would you like to use (Memcheck, Callgrind, Massif)? 

Unfortunately I want to use memcheck which seems to be impossible


Regards,
Mahmood



________________________________
 From: Vasily Golubev <vas...@gm...>
To: "val...@li..." <val...@li...> 
Sent: Monday, August 26, 2013 5:12 PM
Subject: Re: [Valgrind-users] using valgrind at specific point while running	program
 


Hello, Mr. Naderan.

What particular tool would you like to use (Memcheck, Callgrind, Massif)? If callgrind - you can switch off instrumentation at the start and then switch it on at some particular point (or time). In any case, at first - please test your program with:
valgrind --tool=none ./path-to-your-program
If it spends a lot of time then probably Valgrind (like Memcheck, Massif, etc) is useless for you because of time constrains.
I mean: None - is the fastest tool of Valgrind. It doesn't detect any errors, simply run your code.
If it runs quite fast (for you) and you want to collect only call-graph (use Callgrind) - then you can look at parameters for Callgrind.

Vasily




On Mon, Aug 26, 2013 at 12:00 PM, Mahmood Naderan <nt_...@ya...> wrote:

Thanks. To be honest, I didn't understand!
>It seems that with these macros, I can insert them in the specific section of the code. However my problem is different. There are iterative functions. So I want to start valgrind after, say, 0.5 hours of execution to see what is going on.
>
> 
>Regards,
>Mahmood
>
>
>
>
>----- Original Message -----
>From: Konstantin Tokarev <an...@ya...>
>To: Mahmood Naderan <nt_...@ya...>; "val...@li..." <val...@li...>
>Cc:
>Sent: Monday, August 26, 2013 12:17 PM
>Subject: Re: [Valgrind-users] using valgrind at specific point while running program
>
>
>
>26.08.2013, 11:45, "Mahmood Naderan" <nt_...@ya...>:
>> I want to use valrgind at a specific time while my program is running. For example, when I use -O3 it will take 0.5 hours to reach the desired point. When I use -g -ggdb it will take nearly 2.5 hours to reach the desired point.
>>
>> Now if I use valgrind with -g -ggdb, the program is extremely slow and I can not predict when it reach the desired point.
>> What should I do?
>
>Use client requests:
>
>http://valgrind.org/docs/manual/manual-core-adv.html
>
>--
>Regards,
>Konstantin
>
>
>------------------------------------------------------------------------------
>Introducing Performance Central, a new site from SourceForge and
>AppDynamics. Performance Central is your source for news, insights,
>analysis and resources for efficient Application Performance Management.
>Visit us today!
>http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
>_______________________________________________
>Valgrind-users mailing list
>Val...@li...
>https://lists.sourceforge.net/lists/listinfo/valgrind-users
>


-- 
Best Regards,
Vasily

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users