[support]

Hi,

In order to debug your Lib VisualGDB would need 2 things:
1. An AndroidManifest.xml file so that it can know which app to attach to.
2. The libraries with debug symbols put into obj and libs folders, so that VisualGDB can set breakpoints and find code in source files.

You can emulate both by copying the files to the project directory:
1. Copy AndroidManifest.xml file to the directory of your lib project (or to the directory that you specified as a “build directory” when creating the project)
If this does not solve the problem, please attach your AndroidManifest.xml here.
2. Copy your .so file to libsarmeabi
3. Copy your .so file with symbols to objarmeabi

Once this is done, the library project should be debuggable the same way as the app project (including co-debug with Eclipse).
If you have any further difficulties, feel free to post here or contact support directly.

[support]

Hi,

1) Sure. Here’s a tutorial how to do that: http://visualgdb.com/tutorials/android/codebug/
2) Unfortunately, the current version only imports the files from the project directory. Thanks for your feedback, we have put this feature request to the v2.8 plan.

[support]

Hi,

Please use the VisualGDB Project Properties window to make a new configuration. It copies the file correctly.

[support]

Hi,

The Android emulator is the answer here. It is unbelievably slow compared to the actual Android devices. However, note that you would need an actual Windows machine (not a VM) to debug a physical phone or a tablet, as the Android USB driver does not work well with VirtualBox/VMWare.

[support]

Hi,

Building from Eclipse works, as Eclipse uses a separate eclipse-specific build system plugin, while VisualGDB relies on Apache ANT (official command-line build tool for Android).

Looks like your build.xml file is either generated by an old version of Android SDK or has been replaced by some other tool.
Please try deleting it and rebuilding the project. VisualGDB should rebuild the build.xml file automatically.

If the problem persists, please attach the log of the first build (after deleting build.xml) and specify your Android SDK version.

You can also try deleting/renaming the build.properties file.

[support]

Strange. Please attach your build.xml file here or send it to support@sysprogs.com so that we can try to reproduce your problem.

[support]

Hi,

After setting the environment variable you need to restart Visual Studio (or better restart your computer) to get the environment variable propagated.
The problem seems to be quite common for Android SDK (e.g. see here: http://blog.klacansky.com/matter-code/ant-taskdef-class-com-android-ant-setuptask-cannot-be-found).
Could you please attach the D:GabySoftGCodeHexLogicAndroidbuild.xml file here?

[support]

Hi,

The build problem is caused by the ANDROID_SDK_ROOT environment variable. Please go to System Settings, Environment Variables and set a new Environment Variable for the current user:

Name: ANDROID_SDK_ROOT
Value: directory where you have installed Android SDK

Note that VisualGDB 2.8 will provide ANDROID_SDK_ROOT automatically and won’t require this trick any more.

Regarding the breakpoints, there are numerous breakpoint bugs in ndk-gdb and VisualGDB provides workarounds for most of them. If it does not work in your case, please do the following:
1. Open VisualGDB Project Properties (right-click on the project in Solution Explorer).
2. Go to GDB Settings tab.
3. Check the “Log all interaction with GDB” checkbox.
4. Start debugging. Try setting breakpoints.
5. In the GDB Session window run the following commands:

info shared
sharedlibrary

6. Try setting your breakpoints again.
7. Exit debug session.

Then please send all .log files from your project directory to support@sysprogs.com so that we can diagnose your problem further.

[support]

Hi,

The portable WinCDEmu uses a special driver build that does not rely on .inf files.
Try the new experimental build: http://wincdemu.sysprogs.org/portable/PortableWinCDEmu-3.6.exe

[support]

Hi, guys. Sorry for the delay, got far too many things to do.
Try this build: http://wincdemu.sysprogs.org/portable/PortableWinCDEmu-3.6.exe
Note that it has not been through the usual testing cycle, so feel free to report any bugs…

[support]

There are many ways in which the source files can be listed in a Makefile and no possible way to support all of them.
Are you using VisualGDB-generated makefiles or your own makefile layout?

[support]

Hi,

Please change the configuration type to “Makefile project” in Visual Studio project properties (not VisualGDB project properties).

[support]

Hi,

That is by design, as VisualGDB cannot distinguish between source files added by someone else and generated files or temporary files.
Note that this should not stop VisualGDB from building and debugging the project correctly if the Makefile was updated by the person adding a new source file.

[support]

Hi,

Thanks for reporting this problem. Currently VisualGDB does not set ANDROID_SDK_ROOT. You can fix it by setting the variable before running Visual Studio: e.g. make a bat file containing the following lines:

set ANDROID_SDK_ROOT=C:PROGRA~2Androidandroid-sdk
"C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDEdevenv.exe"

We will add the ANDROID_SDK_ROOT support to the next version of VisualGDB.

[support]

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.

[Author]

Posts