Stacktrace for published apps

I have a bug in an app I published as a beta but in the logs I only get a stack trace like

Stack:
- pc: 0x100045ea
- pc: 0x10004505
- pc: 0x10005aa2
- pc: 0x10005a3e
- pc: 0x10005970

which doesn't tell me much. I looked inside the .iq file and there are debug.xml files in the device folders. Should this work or would I have to sideload the app with a separate debug.xml file to get line numbers for the stack race?

Top Replies

jim_m_58 over 4 years ago +1 verified

https://forums.garmin.com/developer/connect-iq/f/discussion/231129/so-you-have-a-ciq_log-file-but-all-you-see-is-pc-without-a-friendly-stack-trace---what-to-do

All Replies

+1 jim_m_58 over 4 years ago

https://forums.garmin.com/developer/connect-iq/f/discussion/231129/so-you-have-a-ciq_log-file-but-all-you-see-is-pc-without-a-friendly-stack-trace---what-to-do

0 Nik over 4 years ago

Thanks! I never actually looked at the debug.xml content but now that I think of it, it's quite logical that it should contain the mapping to actual source code lines

0 jim_m_58 over 4 years ago in reply to Nik

The tricky part is the ciq_log file has it in hex, the debug.xml in decimal, and the address is often between a couple lines.

0 Nik over 4 years ago in reply to jim_m_58

Yes, I noticed that but the right class and a ballpark figure is usually close enough. I had done some major refactoring to around 10 classes and ended up with a "too many arguments" in a call to stuff handling the lightning network which was never called in the simulator but blew up on the device as soon as I started it up

0 Nik over 4 years ago in reply to jim_m_58

But since the line numbers aren't exact, it would be quite hard to look for the "nearest line" if they would be in hex