Forum Replies Created
-
Posts
-
Thanks for the update. It looks like we should be able to support it once requested by a user with an active technical support.
Good to know you found the root cause.
As the issue is triggered by a relatively rare setting, we would only be able to support it if there is an easy way to extract the path mappings from the WSL configuration file and if it’s requested by a user with an active support period (sorry, we could not find any orders associated with your email).
The vagrant warning in the diagnostics console can be safely ignored – it comes from VisualGDB trying to locate virtual machines managed by the Vagrant tool and will indeed appear if you don’t have the tool installed.
No problem and good to know it works.
Our system usually recognizes most reinstallation scenarios and provides temporary activation credit, however as you had previously tried to activate the same 1-seat key on multiple seats, you had used up all temporary credit our system could give.
Thanks for confirming this. We have just retested VisualGDB with WSL on Windows 10 build 1903, however we could not reproduce the issue you described.
Please try running this build: VisualGDB-5.4.106.3193.msi
Then enable the VisualGDB Diagnostics Console, reproduce the problem and check the diagnostic output for the command line used by build the app launcher (search for LinuxAppLauncher.c). Then try running the command line manually and see if GCC reports any errors. Once you pinpoint a specific error, please let us know and we will try to add a workaround for this.
Good to know it works. The new functionality is very new, so minor hiccups are to be expected. If you encounter strange error messages or otherwise broken functionality, please share more details with us and we will try our best to fix it.
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/
