Forum Replies Created
-
Posts
-
I found a clue why the static stack analysis is failing. In the project where I noticed it, the firmware does not start at address 0x0. The project has a bootloader that resides there.
The firmware starts at address 0x10000 and the bootloader jumps to this address.
I cannot provide the ELF-file, but I have provided a simple example project (where the analysis worked) with the other start address, and the analysis fails.Hi,
i can debug the dll now, but that doesn’t really help me (and i don’t really know what happens).
There is the Line 129 in ARMStackUsageAnalyser.cs:
“foreach (var insn in _Host.TryReadInstructions(path.Address))”
where the return of the ‘TryReadInstructions’ with a valid function-address returns zero every time and produces the error message ‘HasJumpsToUnreadableAddresses’.
‘TryReadInstructions’ is somewhere outside the debug context and i can not reach it.
Do you have any further suggestions?
Hi,
the log views:
Running verbose stack analysis for EthernetPhyCheckState…
***Starting code path at 0x00020764 with stack depth = 0
###HasJumpsToUnreadableAddressesI’ve download the project and found the line , the log view point to, but if i try to build it, there are a couple of errors, because the include “using VisualGDBExtensibility;” fails.
The Dissassembly works as expected.
Hi,
is there any solution to this issue available?
If i create a project with STM processors, the “Static Stack Analysis” works correct.
On my Project with the LPC54628, using the LPCXpresso SDK 2.6, i see the same behaviour as above with the message “Function contains jumps to invalid addresses.”.The “Disassembly” view in the memory explorer works correctly.
The toutorial mentions a possibility to adapt the script/tool, but how did I not realize.
Kind Regards
