Forum Replies Created
-
Posts
-
Hi,
Thanks, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1462.msi
Hi,
Thanks, this actually looks like a side effect of one of our fixes on top of the original Clang. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1462.msi
Hi,
It’s hard to say why the paths would be reported incorrectly without seeing the original build output. Please try running the build command manually via command line (outside VisualGDB) and check the paths reported there. If you are not sure, feel free to post the log here and we will help you find the correct settings.
Hi,
Hard so say what could cause that, but good to know it works. If you encounter the problem again, feel free to reopen this topic.
Hi,
For custom build, VisualGDB would actually expect you to configure IntelliSense manually. Hence manually editing the gcc_Debug.h file would be the recommended option.
If it does not help, please try using the ‘Go to definition’ command to locate the macro definition. Also please double-check that you are using the Clang IntelliSense engine and not the native VS one.
Hi,
Thanks for reporting this, we have fixed it in this build: VisualGDB-5.2.16.1459.msi
OK, thanks. We should be able to reproduce and fix it in v5.3. We will post an update here once we have a preview build with this feature.
Hi,
This could be indeed related.
We are actually planning to improve the large directory downloading in VisualGDB 5.3 and will reinvestigate this when adding the new feature. As a temporary workaround, please either try running VS as administrator, or temporarily remove the symlink during synchronization.
Hi,
If it only occurs once every few months, it’s probably easier to just ignore it rather than to try locating the cause. If it starts occurring more often after some specific change, let us know and we will try reproducing it on our side.
Hi,
Yes, you can experiment with the default Windows path for relative paths via VisualGDB Project Properties -> Path Mapping.
Hi,
The Clang IntelliSense caches the old file paths in the global file table in order to speed up the up-to-date check operations. The message can be safely ignored, but you can also simply remove the CodeDB directory to discard the IntelliSense cache.
Hi,
You can use the dump command via the GDB Session window to dump arbitrary memory regions to disk.
Hi,
The user variables are supported starting from the Custom edition. If you are using a lower edition, VisualGDB won’t display the related property pages.
You can always upgrade your edition via http://sysprogs.com/splm/mykey or simply use the Windows environment variables instead if you don’t need the other Custom edition features.
Hi,
It is defined there because VisualGDB normally defines the DEBUG macro for the debug configurations to distinguish them from release ones.
You can simply remove it from the “preprocessor macros” field via VisualGDB Project Properties and click “Apply” to regenerate the gcc_Debug.h file automatically.
