Last edited 2 months ago

How to detect memory leaks: Difference between revisions

imported>Frq07399
mNo edit summary
 
Registered User
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>
{{ApplicableFor
{{ArticleMainWriter | Jean-PhilippeR}}
|MPUs list=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x
|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x
}}
<noinclude></noinclude>


{{ArticleApprovedVersion | Jean-PhilippeR | Jean-PhilippeR, LoicP, AlexandreT | <No previous approved version> | PhilipS - 07Dec'18 - 9880 | 23Jan'19}}
Refer to [[Kmemleak|kmemleak]] article for {{Highlight|Linux kernel space}} and to [[Valgrind|valgrind]] article for {{Highlight|Linux user space}}.


<noinclude>
[[Category:How to trace and debug]]
[[Category:How to trace and debug]]
{{PublicationRequestId | 9880 | 2018-12-07 | PhilipS}}
</noinclude>
</noinclude>
Refer to [[Kmemleak|kmemleak]] article for Linux kernel space and to [[Valgrind|valgrind]] article for Linux user space.

Latest revision as of 15:27, 5 November 2024

Applicable for STM32MP13x lines, STM32MP15x lines, STM32MP21x lines, STM32MP23x lines, STM32MP25x lines


Refer to kmemleak article for Linux kernel space and to valgrind article for Linux user space.