Forum Replies Created
-
Posts
-
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.
Hi,
Please try using the latest VisualGDB 5.3 Preview 3 that contains several improvements to comment formatting.
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.
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.
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.
Hi,
You can upload the dump to our FTP (please create a support ticket to get a temporary FTP login/password).
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?
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.
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).
Hi,
This happens because the latest Android SDK removes support for Ant-based builds and only supports Gradle/CMake for C++ code.
As a workaround please try using this SDK: https://dl.google.com/android/repository/tools_r25.2.5-windows.zip
We will look into extending our new CMake project subsystem to Android projects after the final VisualGDB 5.3 release; until then please use the older SDK as a workaround.
Hi,
Thanks for the dump files, it looks like a memory corruption bug. In order to diagnose it, please try the debug build of the engine: http://sysprogs.com/files/tmp/CppEngineCore64.7z
Once it triggers an error (or an assertion), please create another dump file and send it to us.
P.S. Please use a file hosting service like DropBox (you can encrypt the .7z file and specify the password in the support ticket) instead of attaching large files to the tickets. Large attachments slow down the helpdesk system we are using and hence we limit the attachment size to 4 MB.
Hi,
If your code relies on any STM32-specific code (like HAL), it won’t automatically run on Windows either and will need to be ported using some sort of an abstraction layer (you can manually add Linux configurations to an Embedded project via VS Configuration Manager and then copy the .vgdbsettings file from another Linux project). The amount of porting effort will be the same for both Linux or Windows (the only advantage of running tests on Windows would be no need for a Linux VM, but this is solved with the Windows 10 Linux Subsystem).
Hi,
Please use the -Wl,-Map=… syntax instead. Note that if you are using MSBuild, you can enable map file generation via VS Project Properties -> Linker Settings -> Advanced (not VisualGDB Project Properties).
