You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have downloaded the Puncover tool (thanks for a great tool btw). I ran it on my code, which is running on a ARM Cortex M0 with som ROM code being called. This seems to cause this issue.
When parsing the "nm" output, the Puncover stumbles on an absolute address definition:
Example (there are several):
07f1d989 A __eaabi_uidivmod
...
These absolute values are actually entries into a ROM code section, so they are actually getting called from the application.
How can this be handled correctly in Puncover? I have made a quick-fix in Collector.py::parse_size_lines() method. Simply just add an entry in 'types' for the 'A' type as a TYPE_FUNCTION.
I have downloaded the Puncover tool (thanks for a great tool btw). I ran it on my code, which is running on a ARM Cortex M0 with som ROM code being called. This seems to cause this issue.
When parsing the "nm" output, the Puncover stumbles on an absolute address definition:
Example (there are several):
07f1d989 A __eaabi_uidivmod
...
These absolute values are actually entries into a ROM code section, so they are actually getting called from the application.
How can this be handled correctly in Puncover? I have made a quick-fix in Collector.py::parse_size_lines() method. Simply just add an entry in 'types' for the 'A' type as a TYPE_FUNCTION.
The commit ID is 9eaabf8
The text was updated successfully, but these errors were encountered: