Bug 392261 - Ability to measure memory starting from a point in code ?
Summary: Ability to measure memory starting from a point in code ?
Status: CONFIRMED
Alias: None
Product: Heaptrack
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Milian Wolff
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-24 11:16 UTC by Jean-Michaël Celerier
Modified: 2018-03-26 08:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michaël Celerier 2018-03-24 11:16:09 UTC 
It would be nice if heaptrack had something akin to valgrind / callgrind's CALLGRIND_START/STOP_INSTRUMENTATION. 

Currently the "hotplug" feature is not very reliable: I don't see any allocations taking place at all when they are clearly happenning.
Comment 1 Milian Wolff 2018-03-26 08:10:16 UTC 
yep, I agree that this would make for a nice feature addition. 

could you open another bug for the issue you have with runtime attaching? If possible, explain how I could reproduce the issue to figure out what's going on since it seems to work fine for my tests.