Retrieving Backtraces

IoT Modules Development tools
21

It’s beginning to look to me like there’s a bug in the backtrace retrieval such that it only works once…

ie, once you’ve read a backtrace, DS will do this hanging thing if you try to read it again.

22

No, and it should be indeed: logged for fix in the next one.

23

I’m also having troubles with retrieving backtraces, but from an SL6087 with FW R7.44.0.201008311212.

my Environment:

"DWL","V08b0k","","Sierra Wireless",54744,"061810 16:42","efb16c51","00010000"
"FW","FW_SRC_744_12.SL6087G","R7.44.0.201008311212.SL6087","Sierra Wireless",2146096,"083110 12:12","456cf17c","00020000"
"OAT","1.0.0","xxx","xxx",192248,"030311 09:21","959d77a0","00260000"
 -"Developer Studio","1.2.0.201012171243-R6026"
 -"Open AT Embedded Software Suite package","2.34.0.201009090506"
 -"Open AT OS Package","6.34.0.201007281407"
 -"Firmware Package","7.44.0.201008311212"
 -"WIP Plug-in Package","5.40.0.201007290812"

Error Log:

!ENTRY org.eclipse.core.jobs 4 2 2011-03-03 14:38:48.373
!MESSAGE An internal error occurred during: "Retrieve backtraces".
!STACK 0
java.lang.NullPointerException
	at com.swi.tm.hlservices.backtraces.internal.bundle.BacktraceComponent.getBacktraces(BacktraceComponent.java:51)
	at com.swi.tm.model.targetmanagement.impl.TargetImpl.getBacktraces(TargetImpl.java:1027)
	at com.swi.tm.ui.backtraces.BacktracesPage$2.run(BacktracesPage.java:153)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

So, what to do?

best regards,
Gregor Bader

24

Next DS release will fix a couple of backtrace decoding bugs, including this one.