varun-r-mallya/sysprof
1
0
Fork 0
mirror of https://github.com/varun-r-mallya/sysprof.git synced 2025-12-31 20:36:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add missing id parameters to <section>s so yelp-check validates

Browse Source
This commit is contained in:
Andre Klapper
2017-09-25 18:14:17 +02:00
parent 00887d75db
commit 57b863129e
1 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
help/C/faq.page
View File

@ -3,19 +3,22 @@
type="topic" type="topic"
id="faq"> id="faq">
<section id="what-does-heap-mean">
<info> <info>
<link type="guide" xref="index#faq"/> <link type="guide" xref="index#faq"/>
</info> </info>
<title>What does "In file [heap]" mean?</title> <title>What does heap mean?</title>
<p>This means that sysprof believes a function was called from somewhere in <section id="what-does-heap-mean">
the program's heap (where <code>malloc</code> allocates memory) rather than <title>What does "In file [heap]" mean?</title>
the code section (where executable code normally lives.) There are several
possible explanations.
</p>
<section> <p>This means that sysprof believes a function was called from somewhere in
the program's heap (where <code>malloc</code> allocates memory) rather than
the code section (where executable code normally lives.) There are several
possible explanations.
</p>
</section>
<section id="jit">
<title>JIT (Just in Time) compilers</title> <title>JIT (Just in Time) compilers</title>
<p>Languages like Java can generate executable code while a program is <p>Languages like Java can generate executable code while a program is
@ -23,7 +26,7 @@
situation in this case.</p> situation in this case.</p>
</section> </section>
<section> <section id="optimizing">
<title>Optimizing compilers</title> <title>Optimizing compilers</title>
<p>C and C++ compilers can optimize away information needed to determine a <p>C and C++ compilers can optimize away information needed to determine a
@ -42,5 +45,4 @@
code, use these flags: <code>-ggdb -fno-omit-frame-pointer -O0</code></p> code, use these flags: <code>-ggdb -fno-omit-frame-pointer -O0</code></p>
</note> </note>
</section> </section>
</section>
</page> </page>