[70328 Open] Debugger issues on Android

Elements Fire
1

I’ve noticed a couple of issues when debugging android code with the latest Fire beta (they may predate that version however)

  1. Breakpoints break on the line after the one with the breakpoint set.

  2. Not all locals are shown (either in the debug pane or when they are clicked on in the editor) . Some are but most aren’t. This works much much better when debugging on iOS.

2

Thanks, logged as bugs://70328: Two Debugger issues on Android

3

Can you elaborate on the locals issue?

4

BY which carlo means: can you give a concrete example :wink:

5

I can’t remember know exactly what I was talking about then. I think it may have been that with objects you basically get the object address and that’s it. In VS you can see the members of the object. AFAIK you can’t do that with Fire…you just get:

section: ListViewModelSection * = {<ListViewModelSection: 0x7fe73eb26f20>}

If you hover over/click a member of an object in the code you don’t get it’s value. You can only get the address of the parent object.

6

Ah ok. I don’t have UI for drilling into object members yet. It’s on my list as high prio when I get back to Fire full time later this month. The debug console should already be dumping a lot of details for locals, at least.

7

I do seem to recall that I wasn’t seeing all the local variables on Android that I would expect in the debugger pane. I have just tried to check this again but I can’t get a breakpoint to work right now.

8

if locals ar missing altogether, that’s a bug we’d like a test case for.those should work,

:frowning:

9

Just tried several times, built from clean on both x86-64 and ARM Lollipop Emulators - I can’t get a breakpoint to Fire.

EDIT: Stop On Breakpoints is On.

10

This fails only in Fire, or also from VS?

11

Using the Android emulators in VS in VMWare is rather painful so I haven’t tried.

12

ok. i’ll do some investigations myself, this coming week.