[support]

Hi,

Thanks for the repro. It looks like VisualGDB is getting confused by an unexpected combination of tabs and spaces in your code.

Please try resetting the indentations (by selecting all text and holding Shift-Tab) and then reformatting the document. This should set the indentations properly.

Alternatively you can switch from the Clang-based IntelliSense engine to the regular VS IntelliSense engine via VisualGDB Project Properties to get the regular VS behavior (please note that the VS IntelliSense engine often gets confused by GCC-specific constructs in the embedded code and hence may produce less accurate results).

The comment collapsing is not supported yet, sorry.

[support]

Hi,

The message refers to the X11 – mechanism used to show GUI on Linux systems. Normally SSH should forward those connections to your Windows computer and you would see the GUI locally. This could be broken due to several reasons:

• Missing X11 packages server on the Raspberry Pi
• X11 forwarding disabled by the SSH server
• X11 forwarding disabled in the per-host VisualGDB settings
• X11 permissions not configured properly

A quick workaround would be to select “Show X11 windows on the remote computer” on the Debug Settings page of VisualGDB Project Properties.

[support]

Hi,

You can enable the global verbose mode via Tools->Options->VisualGDB->Common->Output->Verbose Mode.

[support]

Hi,

The answer depends on what exactly you are trying to do. Normally the OpenCV_LIBS variable is exported by the OpenCV library itself and you would need to study its CMakeLists.txt structure to locate the statement that exports it. If you define this variable manually in some of your projects, you could use VisualGDB GUI to edit it, but the exact location would depend on the way the variable is defined.

[support]

Hi,

We would recommend importing a Gradle-based project into VisualGDB (e.g. see this tutorial). Projects created with the VisualGDB project wizard are based on Ant and won’t support Gradle dependencies (we will be switching Android projects to the new advanced CMake project subsystem in the next release and will fully support the latest Gradle).

[support]

Hi,

Thanks, we have tried reproducing this behavior, but could not get any inconsistencies with the comments. Please try attaching the source file to the message (instead of copy-pasting it) to preserve the original formatting and let us know the exact steps to reproduce it (e.g. select Edit->Advanced->Format Document) so that we could look into this.

[support]

Hi,

Please try using the latest VisualGDB 5.3 Preview 3 that contains several improvements to comment formatting.

[support]

Hi,

MS IntelliSense does not support automatic header discovery, so it could be indeed related. You can also try disabling the header discovery via the IntelliSense Settings page of VisualGDB Project Properties.

[support]

Hi,

The debug build is extremely slow (up to 100x slower than release) due to large amount of internal checks and no optimization. So if the problem is 100% reproducible, please consider leaving it overnight until you get a reliable crash. If not, the only other option would be to reduce the bug to a smaller non-confidential project that you could share with us so that we could run the debug build on our side.

[support]

Hi,

Normally just a forward slash (/) should suffice. If you want to define a macro containing a string, you can use the syntax shown below:

E.g. the following code will now compile:

    const char *test = MYMACRO;

Please note that using string literals in macros specified via command line might cause IntelliSense errors that are fixed in the upcoming v5.3 Preview 4.

[support]

Hi,

You can upload the dump to our FTP (please create a support ticket to get a temporary FTP login/password).

[support]

Hi,

The answer depends whether you are using GNU Make or MSBuild. Normally VisualGDB should update the include paths automatically. Perhaps they have been removed and then re-discovered by the automatic header discovery feature?

[support]

Good to know it works. If you encounter further problems, feel free to open another topic.

[support]

Hi,

VisualGDB dynamic analysis currently supports stack usage analysis and real-time watch (visualization of various real-time events).

The address santizer does not work on embedded projects yet. We might be able to support it in one of the upcoming versions of VisualGDB, although we cannot promise anything specific at the current point.

 

[support]

Hi,

We have made a note for this in our backlog, however it won’t be added in v5.3 due to priority constraints (possibly not in v5.4 as well).

[Author]

Posts