microsoft / microsoft/MIEngine

Nnative breakpoints do not work

Open
#403 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
859
Forks
233
Avg merge
1d 6h
Merged PRs (30d)
3

Description

I create app with wizard template "Native-Activity Application (Android)". Compile it as x86, set some breakpoints into 'android_main' and run debug. App was sucessfully deployed into emulator and runs. But breakpoints do not hits, and in breakpoints window appears with empty circles.

Environment:
Visual Studio 2015
CrossPlatform installed. Also i tried to checkout and run MSIEnine project with the same effect.

Emulator:
BlueStacks 2.1.8.5663

shell@klte:/ $ getprop ro.build.version.release
4.4.2
shell@klte:/ $ getprop ro.build.version.sdk
19
shell@klte:/ $ cat /proc/version
Linux version 3.10.30-android-hd (build@Build2) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #1 PREEMPT Tue Mar 22 19:05:48 IST 2016

Build log:
1>------ Rebuild All started: Project: Android2.NativeActivity, Configuration: Debug x86 ------
1> ANDROID_HOME=E:\Android\sdk
1> ANT_HOME=E:\Android\ant-1.9.7
1> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.8.0_101
1> NDK_ROOT=E:\Android\ndk\android-ndk-r11c
1> pch.h
1> android_native_app_glue.c
1> main.cpp
1> Android2.NativeActivity.vcxproj -> c:\Work\test\Android2\x86\Debug\libAndroid2.so

Debug session (with the 'Break All' at end:

Due to its size moved to "paste" service: http://pasted.co/60c83004

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked debug-session output and the reported Android Native-Activity reproduction using the x86 Debug build. Compare breakpoint handling around android_main and the generated libAndroid2.so, then verify whether breakpoints bind and stop during the emulator run; the issue is done when native breakpoints work in this setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
devtools, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.