[support]

Hi,

You need to update the Raspberry to have the compatible libraries like libc and libgcc. If you want to support the original Raspbian image, you need to use the same GCC version that the image has.

[support]

Hi,

Most likely you are using a corrupt image. Please download a fresh image from the Beaglebone website and re-flash it. Regarding IntelliSense, the error messages are caused by Visual Studio’s IntelliSense engine not being able to handle some GCC-specific constructs. We are currently working on a clang-based IntelliSense engine that will resolve this problem. We will be releasing a preview build within the next few weeks. Please feel free to give it a try once it is out.

[support]

Hi,

The “/usr/local/include/opencv” syntax won’t work with a cross-compiler. Please use either the full Windows path (D:/SysGCC/linaro/…/include/opencv) or the ‘=’ syntax (=/usr/local/include/opencv).

[support]

Hi,

First of all, you can increase the timeout before VisualGDB shows that box via Tools->Options->VisualGDB->Tweaking.
The timeout with “-data-evaulate-expression “sizeof(void *)”” is very strange, as this command does not involve communicating to the device, it should be handled locally based on the data from the ELF file. Hence, most likely the problem is in your GDB. You can diagnose it the following way:
* Try using a different version of GDB (selected on the Makefile Settings page)
* Try running the command manually via the GDB Session window. Does it always take that long or only during the first run?
* Select “all GDB interaction” in the GDB Session window and look for strange warnings. Does it take lots of time for GDB to load the initial symbols?
* Does your problem happen on smaller projects? If no, can you strip debugging symbols off some libraries you not currently stepping through? Does this improve performance?

[support]

Hi,

Please try adding the following flags to CFLAGS/CXXFLAGS:
-static-libgcc -static-libstdc++
You can read more about -static-xxx flags here: https://gcc.gnu.org/onlinedocs/gcc/Link-Options.html

[support]

Hi,

You can get the pointer to the active QApplication object via QApplication::instance() method as described here: http://qt-project.org/forums/viewthread/9319
You can link the signals/slots with handlers using the Qt plugin for Visual Studio, however it is not as powerful as the WinForms or WPF editors.

[support]

Hi,

Thanks for letting us know. The texane/st-link tool is not maintained by us, it’s an open-source tool (https://github.com/texane/stlink) that we simply compile and ship as a separate package. Feel free to submit a bugreport on the tool bugtracker.

[support]

Hi,

Thanks for sharing this. You can also select a custom toolchain in the VisualGDB Project Wizard, then VisualGDB will detect your toolchain version correctly and adjust IntelliSense accordingly.

[support]

Hi,

Please try the latest VisualGDB 4.3r2. It contains fixes for some bugs that could be causing this.

[support]

Hi,

Normally VisualGDB should test the toolchain when you modify the build flags on the Makefile Settings page of VisualGDB Project Properties. It will then extract the include directories reported by the toolchain and setup IntelliSense. If that does not happen for you, please check if toolchain testing reports any errors and if the IntelliSense page of VisualGDB Project Properties contains any entries at all.

[support]

Hi,

The templates are stored in XML files inside the “C:Program Files (x86)SysprogsVisualGDBProjectTemplates” folder. Please verify that the folder exists and that you can access it from Visual Studio (e.g. try opening an XML file via File->Open).

[support]

Hi,

What ethernet card are you using? Kgdboe (Ethernet debugging transport) can be incompatible with some cards. What happens if you try setting up KGDBoE manually (http://sysprogs.com/VisualKernel/kgdboe/tutorial/)? Do you get a connection? Do you get any errors in dmesg?

[support]

Hi,

If you are using a Custom or Ultimate edition, you can add a custom pre-build steps to upload as many files/folders as you want. If not, you need to pick one root source directory (so that all source files are located in it or its subdirectories) and set it as your source directory on the Project Settings page of VisualGDB Project Properties.

[support]

Hi,

Is your handler function defined in a C++ file? If yes, it needs to be surrounded by extern “C”:

extern "C" void SysTick_Handler()
{
//...
}

[support]

Hi,

We have investigated this more. When you debug a custom APK file with VisualGDB it checks all EABIs that are present in the APK file and ensures that the library directories for them are present in your library location. Looks like in your case the APK file contains an armeabi version of the libraries, but your library directory does not have them. You can resolve this in one of 2 ways:
* Remove other EABIs from the APK file
* Provide debug versions of all libraries in the APK file for all platforms

You can also press the ‘ignore’ button in the error window to ignore the missing libraries and start debugging nonetheless. If your device EABI is armeabi-v7a, the missing armeabi directories should not affect debugging.

[Author]

Posts