Why do I get incomplete stack traces when debugging via XCode on device?

[ThomasH99]

Hello, maybe it's due to the recent optimizations, or I've misunderstood something, but the stack traces I get on my iOS device (using 7.0.265) are incomplete (or incorrect), e.g. the code at the indicated line numbers does not contain calls to the next line in the stack trace). So, it looks like the trace is missing lines.

As an example in the trace below, the ScreenMain constructor line 135 does not create a new MyTree (but it does call a method X that calls method Y which will create a new MyTree). I would expect to see the calls to X and Y in the trace like it used to be.

Similarly, the line 274 in the MyTree2 constructor does not call MyLog.LOG (but it probably happens somewhere down the call path, only here it is not straightforward to figure out where exactly).

Is this an error and if not, is there a way to still get the full stack trace?

[EDT] 0:0:0,625 - Exception: java.lang.Exception - ASSERTION FAILED node of unknown type=null; type:LOG; level: DEBUG
java.lang.Exception
    at com_myapp_myapp_MyLog.LOG:267
    at com_myapp_myapp_MyTree2.__INIT__:274
    at com_myapp_myapp_ScreenMain.__INIT__:135
    at com_myapp_myapp_DeviceState.startupAfterUserLogin2:1233
    at com_myapp_myapp_myapp.start:3916
    at com_codename1_ui_Display.processSerialCalls:1413
    at com_codename1_ui_Display.mainEDTLoop:1157
    at com_codename1_ui_RunnableWrapper.run:139
    at com_codename1_impl_CodenameOneThread.run:179
    at java_lang_Thread.runImpl:0

[shai-almog]

It's possible that this relates to our virtual method inlining optimization which is a major part of the performance work. All the methods that get remove can't be the source of the exception since we only eliminate methods that can't have side effects.