2020-03-11 03:02 AM
The process is as follows:
Solved! Go to Solution.
2020-03-13 06:59 AM
Actually STM32CubeMonitor is running out of memory when parsing the executable file.
Indeed when parsing the file, our parser is retrieving a variable which is an array of 29605888 unsigned char.
When clicking on "Expand Variable list" checkbox, our parser is trying to retrieve the 29605888 adresses of the array elements.
This array variable retrieved by the arm debugger tool (on which our parser is relying) is located in "..\Utilities\malloc.c" file and names "mem2base":
(gdb) ptype mem2base
type = unsigned char [29605888]
This size is far too high for our parser capabilities then the crash occurs.
As a fix, we will need to limit in our parser the size of the array to expand such as it won't crash anymore when parsing such executable file.
Thanks for raising this issue, and stay tuned for upcoming fix release.
2020-03-11 06:37 AM
Hello 0.Developer,
Could you please provide your axf executable file ?
Thanks !
2020-03-12 06:40 PM
2020-03-12 06:43 PM
Always crashes at 74%~~:face_with_tears_of_joy:
2020-03-13 03:42 AM
Thanks for the file. Likely a bug, currently investigating why this specific file makes the STM32CubeMonitor crashed.
2020-03-13 06:59 AM
Actually STM32CubeMonitor is running out of memory when parsing the executable file.
Indeed when parsing the file, our parser is retrieving a variable which is an array of 29605888 unsigned char.
When clicking on "Expand Variable list" checkbox, our parser is trying to retrieve the 29605888 adresses of the array elements.
This array variable retrieved by the arm debugger tool (on which our parser is relying) is located in "..\Utilities\malloc.c" file and names "mem2base":
(gdb) ptype mem2base
type = unsigned char [29605888]
This size is far too high for our parser capabilities then the crash occurs.
As a fix, we will need to limit in our parser the size of the array to expand such as it won't crash anymore when parsing such executable file.
Thanks for raising this issue, and stay tuned for upcoming fix release.
2020-03-13 06:07 PM
Thanks for your explain, Thierry.
Looking forward to the fix release !