[support]

Could you attach a screenshot of the directory list? What exactly happens when you press the “remove” button?

[support]

Hi,

Not fully sure what you meant. Could you provide a simple example showing file contents and expected/observed IntelliSense suggestions?

[support]

Hi,

Normally “continue” should work. If it does not, please try clicking the “signals” tool button in the GDB Session window. This will open a GDB-specific dialog with GDB signals allowing you to change their handling. If this does not help, please let us know a specific signal that is not working and send us a full GDB log (obtained by enabling debug logging on the GDB Settings page of VisualGDB Project Properties).

[support]

Hi,

You can find the linker workaround option on the Debug Settings page as shown on the screenshot below:

If the test always keeps on failing, could you please run the extended tests via Android->Device Compatibility Center and send us the logs? Perhaps we could find a different workaround.

Based on what you have described, most likely normal debugging will work for you, but if you load libraries dynamically, GDB won’t be able to see them until you run “sharedlibrary” manually.

[support]

Hi,

There might be differences in the MCU initialization code and the external oscillator frequency. Please download the STM32F3 firmware package from ST and check the “Projects” folder for USB projects for your board/device. Then copy the SystemClock_Config() function and usb_conf/usb_desc files from a matching sample project.

[support]

Yes, that should work. Normally if the toolchain is built correctly, it should pick up the sysroot directory from the standard location automatically. If not, specifying –sysroot=xxx (a.k.a. CMAKE_SYSROOT in Cmake) is the way to go.

[support]

Hi,

Thanks for reporting this, we have fixed the problem with the relative paths in VisualGDB 5.0R2. You can download it here: http://visualgdb.com/download/

We have also added an option (currently unsupported via GUI) to disable the use of toolchain files. Please change any setting in VisualGDB Project Propreties, save the settings, open the .vgdbsettings file in a text editor and modify the DisableToolchainFile field.

[support]

Is it the toolchain that came with VisualGDB (http://gnutoolchains.com/arm-eabi/) or have you installed it separately? Could you attach your stm32.xml file that shows the current toolchain configuration?

[support]

Hi,

Thanks for reporting this. Looks like the gdb error message changed in one of the recent versions. We have updated our knowledge base so it should now warn about the missing file.

[support]

Hi,

Please try following the Cocos2d-x VisualGDB tutorial here: http://visualgdb.com/tutorials/android/cocos2dx/simplegame/. It contains all necessary steps. If it does not work for you, please let us know.

 

[support]

Hi,

Are Source.cpp, Source.h and ObjectClass.h in the same directory? If not, it is by design that IntelliSense only searches the include directories and not every possible directory.

If you have imported a custom project, most likely your build system adds those directories to the include directory list explicitly, so build can find them. VisualGDB can only import those directories automatically if you are using VisualGDB-generated Makefiles (or CMake/QMake files) with known structure, otherwise you need to specify the include directories manually like you just did.

[support]

Hi,

Thanks for reporting this, we have fixed it in VisualGDB 5.0R2: http://visualgdb.com/download/

[support]

Hi,

Sorry to hear that it did not work for you. We have rechecked everything and published a detailed tutorial showing how to debug Gradle flavors here: http://visualgdb.com/tutorials/android/astudio/flavors/

We have also released VisualGDB 5.0R2 that contains several fixes related to project configurations in VS2015. Please update your VisualGDB before trying the tutorial: http://visualgdb.com/download/

If this still does not work, please share more details of the problem here or via our support email. We certainly did not intend to break this functionality in v5.0, so if it is broken in any way, we will certainly fix it.

[support]

Hi,

VisualGDB path mappings only affect the error messages and paths reported by the debugger; they do not change the inner logic of the toolchain.

You can use the ‘=’ prefix to specify paths relative to the sysroot, e.g.:

GROUP ( =/lib/libc.so.6 =/usr/lib/libc_nonshared.a  AS_NEEDED ( =/lib/ld-linux-armhf.so.3 ) )

If you need to change the files often, the easiest solution would be to make a simple script for adjusting the paths in the newly copied files. It should be doable with a few regular expressions…

[support]

Please try replacing the msp430.dll file in the toolchain bin directory with the latest version from TI. This should ensure that it is 100% compatible with your hardware.

[Author]

Posts