Forum Replies Created
-
Posts
-
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.
No problem. Most likely this is caused by some other declaration or setting. Please try getting a minimal example that triggers the problem on a newly created project and share it with us so that we could see what is going on.
The error looks correct (the private functions Parent are not accessible to derived classes). You can double-check this by trying to build the project – the compiler should show the same error.
Hi,
Yes, please try running the following command:
<VisualGDB directory>\VisualGDB.exe /build <full path to .vgdbcmake file>
The daily builds with hotfixes do not always pass our internal tests, so some issues are to be expected. That said, the 5.4.106 branch has passed most of the tests and should be much more stable (we are also planning to release a stable R6 update today).
VisualGDB simply requests the target to enable the X11-over-SSH forwarding. The exact implementation of this logic is provided by the target and is outside VisualGDB’s control. Please refer to the Linux and X11 documentation for more details.
