[support]

Hi,

VisualGDB uses the Makefile configuration type in order to allow VIsualStudio use IntelliSense, class diagrams and other similar features just like for normal Makefile-based projects. If you create a new project type and implement IVsBuildableProjectCfg, you should be able to launch VisualGDB for your projects by specifying the VisualGDB port supplier and debugging engine GUIDs in launch options. However in this case you might end up breaking support for IntelliSense and other similar features.

VisualGDB actually has an experimental project extension system that exposes many internal API (e.g. communicating to SSH targets) and allows writing sophisticated build and debug actions in C#. If you could provide us with an overview of your build scenario and explain why the current VisualGDB build process does not cover it, we should be able to help you develop your extension to support it properly.

[support]

Hi,

Please reinstall MinGW selecting “C++ compiler” in the installer options. Alternatively you can use a prebuilt package from http://gnutoolchains.com/mingw32/

[support]

Hi,

Thanks for reporting this. It is a bug in VisualGDB 4.0r3. Please go to VisualGDB Project Properties, Build Settings page and change Targeted Android Platform from android-15 to android-18. We will release a fix resolving this issue in VisualGDB 4.0r4.

[support]

Hi,

Have you added the -std=c++0x flag via the VisualGDB Project Properties dialog? If no, please remove it and add again through the dialog. This will let VisualGDB re-query preprocessor definitions used by GCC and setup IntelliSense accordingly. If everything was detected correctly, your gcc_.h file in the project directory should contain the following definition:

#define __GXX_EXPERIMENTAL_CXX0X__ 1

[support]

Hi,

According to the log you posted, GDB can find the symbols for Application::WidthMonitor::CApplication_WidthMonitor class and cannot find symbols for Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*).
Please check whether the Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*) function (can be also mentioned as _ZN3Lib7ImgProc9CLightBar11DetectEdgesEPN6Camera10TImageInfoE) contains the source code in the disassembly file. If no, please run objdump on the .o file corresponding to the cpp file containing the Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*) function and see whether the source is displayed when dumping the .o file.

Please note that when running the “info line” command you should put the function name, not the function calling statement, e.g.:

info line Lib::ImgProc::CLightBar::DetectEdgesFast

The “info line” command will display the source line number that corresponds to a given function and can be used to determine whether the source line information is available for the given module.

[support]

Hi,

Thanks for pointing this out. We will add an update to our next release. Please let us know whether you need a hotfix before the release.

[support]

Please run the following commands on your Raspberry PI box and provide us with the output:
1. ldd
2. ldconfig -v

Please let us know whether running ldconfig fixes the issue.

[support]

BTW, we have improved our STM32 support in VisualGDB 4.0. A tutorial is available here: http://visualgdb.com/tutorials/arm/stm32

[support]

Can you please create a new project with the default debug method (e.g. GDB simulator) and send us the created files? This will help us analyze your problem and suggest a solution.

Additionally could you please check your firewall settings? Visual Studio process needs to have internet access in order to download additional packages. If this is not possible, we can provide you with instructions on manually downloading and installing those packages.

[support]

Hi,

Which toolchain are you using? Please use our arm-eabi toolchain (it is installed automatically when selected on the toolchain page). Please also note that OpenOCD/J-Link is available starting from VisualGDB 4.0 and won’t work on 3.x.

[support]

How often does this happen? We have encountered similar behavior on some versions of MacOS and it looked like a bug in their end of SSH. Could you build newer GDB from sources in your home directory and let VisualGDB use it explicitly?

[support]

Thanks for reporting this. We have fixed it in Beta 3.

[support]

Hi,

Thanks for your explanations. We have fixed it in Beta 3. We have also added an option (Tools->Options->VisualGDB->General) to override the default file masks used when creating projects.

[support]

Hi,

Thanks for reporting this. Could you please let us know how what exactly you are doing to browse the folder? Please feel free to attach a screenshot or a step-by-step description.

[support]

Hi,

First starting the app and then attaching to it is the default behavior of the Android debugger.
You can override it by selecting Android->Debug Options->Debug App Startup in Visual Studio.
Once you select that option, starting debugging will take slightly longer, but all your initialization breakpoints will be hit.

[Author]

Posts