We are currently struggling to receive backtraces from our firmware. With the sample program (bug.c) can successfully retrieve all backtraces. We initially thought it might have something to do with c++ but after converting the sample program to a small c++ program and running that all backtraces were successfully retrieved. Dont know if it’s due to the complexity/size of our program (305 KB with ± 50.cpp and header files). When trying to retrieve backtraces with our firmware retrieval doesn’t move past 0% (Loading unwinding data) even when left overnight and the only way to kill it is to restart the DS the cancel button does nothing. No errors are logged in the .log file either. I know why the program crashes and fixed this bug but if an unknown one appears will not know where to start looking.
Other methods tried with some success:
ADS Bckt -> Rtk11_Schedule : 0x00001383 ADS Bckt -> rtk_TaskStackOverflow : 0x000644D3 ADS Bckt -> RtkExceptionRoutine : 0x0006518B ADS Bckt -> KER_ERROR_DIAGNOSE : 0x000342A9 ADS Bckt -> KER_VERROR_DIAGNOSE : 0x000341F3 ADS Bckt -> sys_BackTrace : 0x00066B10 ADS Bckt -------> ADS BACK TRACE <------- ADS Bckt The function corresponding to this address : 0x3c8c, is not in the .axf file Trace SYS 1 Current OAT Task index : 0 Trace CUS4 1 ARM Data Abort caught at 0026B214, Current Task 0x1F by CP15 ADS Bckt -> Unresolved symbol : 0x0026B214 ADS Bckt -------> ADS BACK TRACE <------- ADS Bckt The function corresponding to this address : 0x180c6da8, is not in the .axf file
But dont know if im on the right track or if im going nowhere.
See other people have had the same problems was hoping someone found out how to solve it:
Any alternative methods I can try or advice would be appreciated.
Embedded Module: SL Series (SL6087)
Open AT OS Package: 188.8.131.52108111228
Open AT Embedded Software Suite Package: 184.108.40.206108306638
Developer Studio: 220.127.116.11103101643-R6604
OS: Windows 7 64-bit