[support]

Hi,

Please run the “info sources” command as described here.
The command will list all source files known by GDB and will probably answer why r:/Projects/VA128//jni/arch_android.cpp is not accepted.
Feel free to post the “info sources” output here.

[support]

Unfortunately, IAR compiler generates debugging data in a format that is incompatible with GDB. Thus, VisualGDB cannot debug it.
However, we could help you switch your project to the GCC toolchain. The toolchain is stable, widely used by community and we can answer your questions on GCC-specific syntax.

[support]

Hi,

Yes, we support VS2012 starting from v2.7.

[support]

Thanks for the feedback. Currently it is not supported, however we have added it to v2.8 feature list.

[support]

Hi,

Normally it is supported. However, it might not work if your GDB does not report any locals. Please create and send us a GDB log file so that we can tell you how to fix the locals in your case.

[support]

Yes, this is supported since v2.4. If you are encountering problems with your version of the STL library, please provide us a screenshot of the expanded watch window so that we can diagnose your problem further.

[support]

Hi,

Those files are generated from the IDL file by the MIDL compiler. This should happen automatically when you build the project with Visual Studio.

[support]

Hi,

The Android GDB provided by Google is VERY slow. If your library size is 18MB, it might take several minutes to load the symbols. When VisualGDB displays this warning, the operation is still running in the background, so the window will disappear after some time.

[support]

Hi,

For the first month, yes. If you upgrade later than 1 month after buying, the upgrade cost will include additional fees for extending your support period that are proportional to the time difference.

[support]

Hi,

Essentially, the Custom Edition unlocks the “Full Custom Configuration” menu in the Project Wizard. If you have not used it so far, Network Edition should suit your needs.

Below are the detailed answers to your questions:

1. With the Network Edition VisualGDB will only do the following to build your project:
a. Copy source files
b. Run a command line you have specified
When you debug a project it will also run 1 command line that you provide.

With custom edition you can specify command lists (e.g. copy multiple directories, run some commands before/after GDB and so on). Essentially, you can do all of it with your custom script and tell the Network Edition to run it. However, if you plan to do those things frequently, the Custom Edition might save you some time by automating it.

2. “Start GDB interactively” refers to the “Start custom GDB session” in the Debug menu in Visual Studio. It is only useful if you want to experiment with various GDB settings without modifying project settings.

3. “Multiple build machines” refers to the full-custom configuration. With the Network Edition “build project” means “transfer files and execute 1 command line specified by you”. The command line can be arbitrary and can invoke any tools you wish. With the Custom Edition you could use VisualGDB functionality to run several commands on different machines (e.g. build your app on Linux machine A, then transfer it to Linux machine B and run GDB on machine B).

4. Custom GDBSERVER-like setup means that VisualGDB will
a. Run your program that opens a connection on some port
b. Run GDB so that it attaches to that port
c. When GDB exits, VisualGDB will run another command line to stop the first program

You can script all of that yourself as well and let VisualGDB just start your script…

5. Yes, you can assign shortcuts to VisualGDB commands by using Visual Studio Options window as described on the FAQ page: http://visualgdb.com/support/faq.php

If you have any further questions, feel free to contact support or ask on the forum.

[support]

Hi,

Based on the log you have provided, some data gets lost between your PC and the Android device, so that GDB cannot really debug it.
This might happen if you are running VisualGDB inside a VM or if it can be also caused by a buggy device driver.

Are both devices using the same driver (according to Windows device manager)? Is there any software on your computer that might try to access the Android device on its own and thus interfere with debugging?

[support]

That is strange. Please send us an archive containing the following files from your project/solution:

1. *.sln
2. *.vcproj
3. *.vgdbsettings

This will help us reproduce the problem on our side and provide you with a solution.

[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.

[Author]

Posts