blocks|key|385939|text|我更喜欢在linux上使用the+valgrind++heap+profiler：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|385940|valgrind+--tool=massif+./testprogram|code-block|syntax|javascript|385941|然后,|385942|ms_print+./massif.out.16766+#+replace+with+actual+generated+name|385943|385944|19.63%5E+++++++++++++++++++++++++++++++++++++++++++++++###++++++++++++++++++++++
+++++%7C+++++++++++++++++++++++++++++++++++++++++++++++#++++++++++++++++++++++++
+++++%7C+++++++++++++++++++++++++++++++++++++++++++++++#++::++++++++++++++++++++
+++++%7C+++++++++++++++++++++++++++++++++++++++++++++++#++:+:::+++++++++++++++++
+++++%7C++++++++++++++++++++++++++++++++++++++:::::::::#++:+:++::+++++++++++++++
+++++%7C++++++++++++++++++++++++++++++++++++++:++++++++#++:+:++:+::+++++++++++++
+++++%7C++++++++++++++++++++++++++++++++++++++:++++++++#++:+:++:+:+:::++++++++++
+++++%7C++++++++++++++++++++++++++++++++++++++:++++++++#++:+:++:+:+:++::++++++++
+++++%7C++++++++++++++++++++++++++++:::::::::::++++++++#++:+:++:+:+:++:+:::+++++
+++++%7C++++++++++++++++++++++++++++:+++++++++:++++++++#++:+:++:+:+:++:+:++::+++
+++++%7C++++++++++++++++++++++++:::::+++++++++:++++++++#++:+:++:+:+:++:+:++:+::+
+++++%7C+++++++++++++++++++++@@@:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C+++++++++++++++++++::@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C++++++++++++++++::::+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C++++++++++++++:::++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C++++++++++++:::+:++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C+++++++++::::+:+:++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C+++++++:::++:+:+:++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C++++::::+:++:+:+:++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++++%7C++:::++:+:++:+:+:++:+@++:+++:+++++++++:++++++++#++:+:++:+:+:++:+:++:+:+@
+++0+%2B----------------------------------------------------------------------->KB+++++0+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++29.48

Number+of+snapshots:+25
+Detailed+snapshots:+[9,+14+(peak),+24]|385945|故障会是这样的|385946|--------------------------------------------------------------------------------
++n++++++++time(B)+++++++++total(B)+++useful-heap(B)+extra-heap(B)++++stacks(B)
--------------------------------------------------------------------------------
+10+++++++++10,080+++++++++++10,080+++++++++++10,000++++++++++++80++++++++++++0
+11+++++++++12,088+++++++++++12,088+++++++++++12,000++++++++++++88++++++++++++0
+12+++++++++16,096+++++++++++16,096+++++++++++16,000++++++++++++96++++++++++++0
+13+++++++++20,104+++++++++++20,104+++++++++++20,000+++++++++++104++++++++++++0
+14+++++++++20,104+++++++++++20,104+++++++++++20,000+++++++++++104++++++++++++0
99.48%25+(20,000B)+(heap+allocation+functions)+malloc/new/new[],+--alloc-fns,+etc.
->49.74%25+(10,000B)+0x804841A:+main+(example.c:20)
%7C+
->39.79%25+(8,000B)+0x80483C2:+g+(example.c:5)
%7C+->19.90%25+(4,000B)+0x80483E2:+f+(example.c:11)
%7C+%7C+->19.90%25+(4,000B)+0x8048431:+main+(example.c:23)
%7C+%7C+++
%7C+->19.90%25+(4,000B)+0x8048436:+main+(example.c:25)
%7C+++
->09.95%25+(2,000B)+0x80483DA:+f+(example.c:10)
++->09.95%25+(2,000B)+0x8048431:+main+(example.c:23)|385947|entityMap|0|LINK|mutability|MUTABLE|url|http://valgrind.org/docs/manual/ms-manual.html^0|D|R|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|16|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|18|8|@]|9|@]|C|$]]|$1|N|3|O|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|P|3|Q|5|6|7|1A|8|@]|9|@]|C|$]]|$1|R|3|S|5|F|7|1B|8|@]|9|@]|C|$G|H]]|$1|T|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|U|$V|$5|W|X|Y|C|$Z|10]]]]

I prefer to use <a href="http://valgrind.org/docs/manual/ms-manual.html" rel="nofollow">the valgrind massif heap profiler</a> on linux:

<pre><code>valgrind --tool=massif ./testprogram
</code></pre>

Then, 

<pre><code>ms_print ./massif.out.16766 # replace with actual generated name
</code></pre>

Will give you a chart with samples and peak heap usage, and a breakdown like so

<pre><code>19.63^ ### 
 | # 
 | # :: 
 | # : ::: 
 | :::::::::# : : :: 
 | : # : : : :: 
 | : # : : : : ::: 
 | : # : : : : : :: 
 | ::::::::::: # : : : : : : ::: 
 | : : # : : : : : : : :: 
 | ::::: : # : : : : : : : : :: 
 | @@@: : : # : : : : : : : : : @
 | ::@ : : : # : : : : : : : : : @
 | :::: @ : : : # : : : : : : : : : @
 | ::: : @ : : : # : : : : : : : : : @
 | ::: : : @ : : : # : : : : : : : : : @
 | :::: : : : @ : : : # : : : : : : : : : @
 | ::: : : : : @ : : : # : : : : : : : : : @
 | :::: : : : : : @ : : : # : : : : : : : : : @
 | ::: : : : : : : @ : : : # : : : : : : : : : @
 0 +-----------------------------------------------------------------------&gt;KB 0 29.48

Number of snapshots: 25
 Detailed snapshots: [9, 14 (peak), 24]
</code></pre>

The breakdowns would be like

<pre><code>--------------------------------------------------------------------------------
 n time(B) total(B) useful-heap(B) extra-heap(B) stacks(B)
--------------------------------------------------------------------------------
 10 10,080 10,080 10,000 80 0
 11 12,088 12,088 12,000 88 0
 12 16,096 16,096 16,000 96 0
 13 20,104 20,104 20,000 104 0
 14 20,104 20,104 20,000 104 0
99.48% (20,000B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
-&gt;49.74% (10,000B) 0x804841A: main (example.c:20)
| 
-&gt;39.79% (8,000B) 0x80483C2: g (example.c:5)
| -&gt;19.90% (4,000B) 0x80483E2: f (example.c:11)
| | -&gt;19.90% (4,000B) 0x8048431: main (example.c:23)
| | 
| -&gt;19.90% (4,000B) 0x8048436: main (example.c:25)
| 
-&gt;09.95% (2,000B) 0x80483DA: f (example.c:10)
 -&gt;09.95% (2,000B) 0x8048431: main (example.c:23)
</code></pre>

blocks|key|385949|text|结构的直接sizeof()将返回编译时的大小，即它不会考虑容器的实际大小。因此，您可能希望手动迭代每个容器，并将每个元素的大小相加。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|385950|但对你来说更简单的方法可能是使用profiler+(例如gprof+(GNU+Profiler))或其他|385951|entityMap^0|5|8|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Straight <code>sizeof()</code> of struct will return compile-time size, i.e. it will not take in consideration actual size of containers. So, you probably want to manually iterate through each container and add up sizes of each element.

But easier way for you is probably to use profiler (e.g. gprof (GNU Profiler)) or any other

I have two questions:

1.) I want to do memory profiling of my code in a function-wise manner. The code can have any STL containers. Is there a way of doing this in linux?

2.) The second one is due to my naivety!! If I have a data-structure

<pre><code>template &lt; class T1 &gt; struct somestruct
{
std::set &lt; T1 &gt; v1;
std::vector &lt; T1 &gt; v2;
std::vector &lt; T1 &gt; v3;
};
</code></pre>

and I know the sizes of v1, v2 and v3 then can I do a straightforward calculation of the size of the structure based on sizeof(T1) or would I have to take care of padding?

How to determine size of data (allocated and deallocated) during runtime

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有两个问题：1.)我想以函数的方式对我的代码进行内存分析。代码可以有任何STL容器。在linux中有没有办法做到这一点？2.)第二个原因是我太天真了！如果我有一个数据结构template < class T1 > struct somestruct{std::set < T1 > v1;std::vector < T...

问如何在运行时确定数据大小(已分配和已释放)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在运行时确定数据大小(已分配和已释放)EN