Forum Replies Created
-
Posts
-
Please note that our support is limited to VisualGDB issues only. We can point out the location of various settings, however we cannot guarantee that every project opened with VisualGDB will build correctly, sorry. Our best advice would be to make sure you understand the structure and requirements of the project and can build it outside of VisualGDB first.
We have provided them with an updated build that follows their instructions and still reproduces the problem on December 17th and have not heard from them since then. Please consider contacting Microsoft support directly, or posting on the bug tracking page to speed it up. We have done everything we could on this one (short from designing our own replacement Call Stack window) and the delay is on their side.
As a side note, a 100% working (although annoying) workaround would be to delete the watch expression that triggers the error, and switch back and forth between the threads via Debug->Windows->Threads. This makes the call stack reappear.
Sorry about that. If the file is too large, would you be able to upload it to a file hosting service (e.g. DropBox) and share a link?
Hi,
No problem, we should be able to investigate it if you could attach the .atzip file (please rename it to .zip to avoid attaching problems) and share the instructions to reproduce the problem (e.g. what to select in the wizard).
Hi,
We have confirmed the problem. It happens because the VeriSign timestamping service used by VisualGDB to sign the generated drivers with a temporary certificate stopped working. We have updated VisualGDB to use a different timestamping service. Please try this build: VisualGDB-5.5.104.3936.msi
Hi,
Sorry, our support covers VisualGDB issues only. We are not able to help troubleshoot specific projects without directly billing for the time required to do such troubleshooting.
Please consider posting on Qt and/or Beaglebone forums for further help with this.
Hi,
According to our records, your trial period has expired. If you would like to get further support, please consider purchasing a license.
The “::” syntax is a known limitation of the C++ parser used in our Natvis engine. As a workaround, please consider using the “(::Type)(Expression)” or “static_cast<Type *>(Expression)” syntax. As the issue only affects a very small number of users, and the workaround fully solves the problem, we will not be able to change our parser to address it.
VisualGDB is licensed per seat (computer/user combination). If you would like multiple users to use VisualGDB on the same terminal server, each of them would need a separate license. For your convenience, you can always purchase a multi-seat license key that will get activated on the number of seats you purchased.
No problem, please try this build: VisualGDB-5.5.104.3933.msi
You can set the new Tools->Options->Text Editor->C/C++(VisualGDB)->Formatting Engine->Ignored clang-format statements option to AfterCaseLabel and VisualGDB will automatically filter out any lines containing AfterCaseLabel (the check is case-sensitive) when loading clang-format files. You can separate multiple values via semicolons.
Hi,
Please try using the $() syntax with environment variables (e.g. $(ProgramFiles) or simply define your own variable).
Also VisualGDB will automatically install Python to $(LOCALAPPDATA)\VisualGDB\Python if you create a project using mbed, esp-idf or nRFConnect, so you can try referencing that Python installation instead.
The loading and applying of formatting styles is done by the clang-format directly and is outside of VisualGDB control. The best thing we can offer is to add a setting to filter out lines containing specific substrings in the clang-format file (e.g. you can blacklist
AfterCaseLabel) and VisualGDB will automatically remove that entire line from the .clang-format file before passing it to the clang engine.Hi,
Our clang-format-based formatter is indeed based on an older version of Clang (6.0). All options supported by this version should work out-of-the-box. We will update it to use a newer Clang version in the next major VisualGDB release, so the newly added options will work as well.
Hi,
VisualGDB inherits the regular Visual Studio experience when it comes to libraries:
- You can use the Add->Existing Item command in Solution Explorer to add existing files (including .a libraries) to a project.
- You can use the VS Project Properties -> C/C++ -> Preprocessor -> Include Directories to specify directories with header files.
Hi,
Thanks for the suggestion. We will consider it in the future, however as the Kendryte devices are very niche, we will likely not be able to do it in the near future.
