Forum Replies Created
-
Posts
-
Hi,
You can specify additional parameters to make by right-clicking on the project in Solution Explorer, selecting “VisualGDB Project Properties” and specifying additional ndk-build arguments. The ndk-build.cmd is currently fixed and cannot be changed via settings. If you want to use a custom build script instead, please write a letter to support@sysprogs.com, we’ll send you a custom build that can do it.
As mentioned before, please send us the GDB log so that we can actually see what’s happening and give you more advice
Hi,
That’s strange. Uninstalling the app should normally reset the state.
As mentioned before, please send us the GDB log so that we can actually see what’s happening and give you more advice.Hi,
There’s a bug in the NDK version of GDB that causes breakpoint problems. VisualGDB fixes it for obvious cases like the JNI directory, but probably does not fix it for your project.
Please open the GDB Session window, select “All interaction with GDB” and try settings your breakpoints. Then send us (or post here) the contents of the GDB Session window. It will contain the GDB commands and replies related to the breakpoints and will help us determine why your breakpoints are not working.You can also try executing the “sharedlibrary” and “info shared” commands in the GDB session window to ensure that your symbols are loaded correctly.
Hi,
You can fix this by adding the following line to Android.mk just before the “include $(BUILD_SHARED_LIBRARY)” line:
LOCAL_SHORT_COMMANDS := trueHi,
Sorry for the late reply.
VisualGDB cannot start debugging because the NDK build system fails to include gdbserver[/b[ into the application package. It might be related to your build problem.
Does the “*** target pattern contains no `%’.” message always appear? Does reinstalling NDK help?Looks like some old version of make.exe gets invoked. Could you please paste the entire build log here?
We are currently working on resolving VS2012 compatibility issues. Does the debugging work with VS2010?
Hi,
It’s a bug of the Android run-as tool. See this page for possible workarounds.Hi,
Which version of NDK and SDK are you using?
Are you using a custom Android.mk file? Could you please post it here or send to the support email?
