Forum Replies Created
-
Posts
-
No problem, we have investigated the Ctrl+Click interfaces used by Visual Studio 2017/2019 and were able to support them from the Clang engine. Please try this build: VisualGDB-5.4.106.3192.msi
You can control whether the suggestion combo box appears by clicking the button with the lightning icon in the bottom left part of the popup. VisualGDB would normally ask whether you want to display the completion popup automatically or manually (by pressing Ctrl-Space) when you use the Clang IntelliSense first time, so most likely you have accidentally selected the manual option there.
Hi,
No problem, we can help you. Please share a screenshot of your Help->About VisualGDB window and a screenshot of the exact error message you get and we will look into this.
Hi,
According to our records, you have recently tried activating your single-seat key on 6 different seats, hence the VisualGDB’s activation logic indeed denied further activations.
We have also not found any tickets from your email address in our system on 2019-03-04. Please double-check the email address you used at that time.
We have received 2 tickets from you today and will respond to you per email with available options in the next 1-2 hours.
Hi,
Sorry about that, the Clang IntelliSense indeed handles some commands slightly differently from the native VS IntelliSense (mostly because it has to use older internal interfaces for backward compatibility with older Visual Studio versions).
The Ctrl-Click is unfortunately not supported, however you can use the regular Go-to-definition command, or the “Go to” button in the top right corner of the edited source file.
The templates for the ‘for’ loop and other common code constructs should normally work, unless they are filtered out via the buttons at the bottom of the suggestion popup. If they do not appear in the suggestion list, please share a screenshot of the entire VS window demonstrating the problem and we will try to suggest a workaround. Another way to display them would be using the Insert Snippet command (Ctrl-K, Ctrl-X).
Hi,
As the message suggests, please double-check that your WSL installation has gcc installed. You can check it by running “gcc -v” from the bash prompt.
Strange, it is based on the same codebase as the ESP32 version.
Could you please try replacing just the bin folder and check if this solves the problem. If not, does combining the VisualGDB’s version of the bin folder with the Espressif’s version of the share folder work?
Please try checking the SQLite documentation for the exact name of the library file (e.g. libsqlite.a or libsqlite.so). Then use the “-l<name without extension and lib prefix>” syntax. Please do not use the ${} syntax, as it implies expanding a non-existent CMake variable.
You can read more about the linker input format and library names on this page: http://visualgdb.com/support/linkerinputs/
Hi,
If you are using an advanced CMake project, please locate your executable (console icon) in Solution Explorer, right-click on it and select “Properties”. Then add the “;-l<library name>” (e.g. -lmysql) to the Linker->General->Linked Libraries field.
Hi,
If you are using the Custom edition, you can add a post-build step that will upload arbitrary files or directories to the target after the build, or add it as a custom shortcut (a new menu entry for it will appear under the Project menu). If not, consider setting the gdb command line to something that will exit immediately and then configuring VisualGDB not to show the “gdb exited” warning.
Just wanted to share an update that VisualGDB now officially supports referencing the ESP32 Arduino core from ESP-IDF projects. We have published a detailed tutorial here: https://visualgdb.com/tutorials/esp32/arduino/component/
Sorry, the only way we can manage the large amount of inquiries we receive and ensure fast turnaround for VisualGDB fixes is by being upfront and strict about the scope of our technical support. Troubleshooting Linux configuration issues can be tricky and there are numerous online resources that could help with that, but unfortunately it is not realistic for us to offer this type of help as a part of our regular product support.
If you can confirm that the problem doesn’t happen when running the program manually, but does happen with VisualGDB, we can help you understand the differences and configure VisualGDB to replicate the working setup. If the problem also happens without VisualGDB (or if another problem is preventing the programs from running on that target), unfortunately this is not something that could be easily fixed by VisualGDB and hence is not covered by our support, sorry.
If running the program directly results in a segmentation fault, the device configuration might be corrupt. Unfortunately, as this is not something controlled by VisualGDB, this is not covered by our technical support.
Welcome back!
Please try updating to VisualGDB 5.4R6. We have recently added support for importing the ESP32 Arduino core into the ESP-IDF projects (see this tutorial).
Generally, the internal structure of ESP-IDF and other related components changes very fast, so the steps that worked for a specific version may stop working for future ESP-IDF releases.
