[support]

Hi,

Unfortunately the GCC compiler does not emit enough information about defines to parse them during debugging. However, VisualGDB has a separate mechanism of tracking peripheral register names and replacing them with the corresponding expressions in the Watch window. If your register is not recognized, you can try editing the device definition files in %LOCALAPPDATA%VisualGDBEmbeddedBSPsarm-eabicom.sysprogs.arm.stm32devices (you can unzip the xml.gz file and just keep the .xml one, VisualGDB will use it automatically).

[support]

Hi,

Could you please check your virtual COM port settings on the virtual machine? Does the COM port number there match the number in VisualKernel settings? Could you please attach the screenshots of both COM port settings dialog and the VisualKernel debug settings dialog?

BTW, if you are using VMWare, it is recommended to use VMWare GDB stub (http://sysprogs.com/VisualKernel/tutorials/vmware/) instead of a virtual COM port, as it’s much faster and more reliable.

[support]

Hi,

The easiest way to have a pre-build action without using the custom edition features would be to change the make command to run a bat file that first runs your custom command line and then invokes GNU make. It is not as convenient as the pre-build action list, but may work for some basic scenarios.

[support]

Hi,

Could you determine which include file causes this? Does it still happen on a default “hello, world” project? Could you share a screenshot of your IntelliSense settings page of VisualGDB Project Properties?

[support]

Hi,

Do you mean the pre-build steps in VisualGDB Project Properties? They are only available in Custom and Ultimate editions. If you were using a trial before and then bought a lower edition, the options would go away after the trial expires.

[support]

Hi,

Please refer to the following topic regarding precompiled header support: viewtopic.php?f=5&t=2769

[support]

Hi,

The main reason why we did not add this feature is because VS is extremely slow when dealing with projects containing lots of source files. Simply opening a project containing the entire Linux kernel can take several minutes, adding the files one-by-one using VS interfaces would take more than 3 hours. The new recursive import feature solves this by closing the solution file, modifying it manually and reopening it, but that would still degrade project opening performance if lots of files are added. Please try using the new recursive import feature and if you don’t notice considerable delays when using it manually, let us know so that we could add an option to run it automatically when new files are detected.

[support]

Hi,

VisualGDB stores the list of source files in the Makefile itself that is shared between configurations. Configuration-specific flags are stored in .mak files that are not affected by adding/removing source files.

[support]

Hi,

In order to use GDB from a different machine you will need to set the ‘allow choosing build/clean/debug command hosts independently’ checkbox on the Project Settings page.
Note that if you don’t want to use gdbserver, you need to disable the ‘deploy executable’ checkbox on the Project Settings page and deploy it manually by adding a file transfer action to pre-debug steps.

[support]

Hi,

That’s a bit strange as both tools use the same SSH engine. Are you using different users with different shells?

[support]

Hi,

Do you mean the toolchains for building windows applications with MinGW or are you talking about some embedded ones?

[support]

Hi,

We’ve added a new command called ‘import folder recursively’ to VisualGDB 4.2 that allows importing an existing folder with subfolders. You can get a quick impression of it by looking at our USB tutorial (http://visualgdb.com/tutorials/arm/stm32/usb/). You can just point it to the main project directory and it will add missing files to the project while keeping all the folder structure. Does that suit your needs or do you want something more sophisticated?

[support]

IntelliSense include directories are usually stored in the absolute form. You can see the exact form of them by looking at Visual Studio (not VisualGDB) project properties on the NMake page. If they contain absolute paths, you can change them to using $(ProjectDir) or modify them to point to the new location.

[support]

Hi,

IntelliSense directories are stored in Visual Studio Project Properties. The fastest way to copy them is to open the VS properties window, go to the NMake page and copy/paste them there.

[support]

Yes, we are working on an independent clang-based C++ IntelliSense engine, but it is not included in VisualGDB 4.2 and will be available at a later point.

[Author]

Posts