System Error stack trace address is way out of range of debug.xml.

I'm back, looking for help.

The stack trace address 0x30003758 is way, way out of range the entries in my debug.xml.

Error: System Error
Details: 'Failed invoking <symbol>'
Time: 2019-06-24T00:19:49Z
Part-Number: 006-B2697-00
Firmware-Version: '13.30'
Language-Code: eng
ConnectIQ-Version: 3.0.11
Filename: 96G15439
Appname: raceQs
Stack:
  - pc: 0x30003758
  - pc: 0x3000340f
  - pc: 0x100046d3

The third entry, pc: 0x100046d3 is near function getValue(index) in my PickerFactory.

I have laced my code with printlns and the last one I get is from within the PickerDelegate initialize.

It crashes on the sim in and on the device (F5) with SDK 3.0.11 and 3.0.12

It worked before the last revision, so something I have done has triggered the issue, but I'm jiggered if I can spot it. The corrupted stack trace doesn't help.

Here's the module

drive.google.com/.../view

(Unable to post as code, the Captcha dialog is corrupted - Safari, Mac)

Alan.raceQs over 7 years ago

OK, I've returned to the earlier version to find that whilst it once again runs on the device (F5), it crashes on the Sim with an odd "Stack: Symbol Not Found" error:

Error: Symbol Not Found Error
Details: Failed invoking <symbol>
Stack: Symbol Not Found Error

(I suspect that is caused by the odd stack address noted earlier which was way out of range of the debug.xml.)

For me, this is an early foray into the use of the Picker, and I'm wondering if there's something amiss. I was always a little suspicious about the fact that the doco is incomplete, and recommends
"Note:See the Picker sample distributed with the SDK for an example of the use of the PickerDelegate class".

Is anyone using it successfully?

Former Member over 7 years ago

The 0x3xxxxxxx address range points to API methods built into the VM. The 0x100046d3 address should point to an API call, such as Communications.makeWebRequest()

Providing this stack trace and some information about what API is being called and is happening in the code that calls it (what the parameters likely are), should help the team track down the cause of this System Error. I'd recommend posting this as a Bug Report because System Errors don't usually indicate an error in your application, but rather in the VM.

Alan.raceQs over 7 years ago in reply to Former Member

I think I have covered these points.

As mentioned in the initial post, 0x100046d3 is near function getValue(index) in my PickerFactory, and I have posted the code.

I'll raise it as a bug, but meanwhile my development along this path is stalled so any suggestions as to a work-around would be helpful.