Forum Replies Created
-
Posts
-
Hi,
Please do check the page we linked in the previous reply – it shows the exact setting for this exact behavior.
Hi,
You can also try using DWARF 5. It is considerably different from DWARF4 and might work around the issue. Another thing to try would be using GDB indexes.
You can troubleshoot the slow gdb response by running the “set debug remote 1” command and checking whether the delay comes from the target answering GDB requests (e.g. OpenOCD) or gdb itself (i.e. happens between a reply and the next request).
Hi,
Our fork of OpenOCD mainly focuses on improved integration with VisualGDB (e.g. faster memory reading API for VisualGDB to use) and does not duplicate any of VisualGDB’s features on its own.
Hi,
Please refer to the following page for more details: https://visualgdb.com/documentation/colors/
Hi,
Sure, you can always click the “select a third-party toolchain” button to import an arbitrary toolchain. VisualGDB will create a Toolchain.xml/CustomToolchain.xml file either in the toolchain directory or under %LOCALAPPDATA%, where it will store the toolchain properties. You can then manually edit the file to customize various settings (e.g. add hardcoded CFLAGS). See this page for a detailed explanation.
Hi,
The OpenOCD implementation of semihosting is rather unreliable, hence VisualGDB provides its own one. Naturally, it will only work when using VisualGDB for debugging.
If you are able to connect (and successfully use) gdb to OpenOCD when you run it manually, please share the following:
- The exact command lines from OpenOCD and GDB from the manual debug session that works.
- The OpenOCD and GDB command lines shown by VisualGDB/VisualKernel. You can find the OpenOCD command line in OpenOCD window in Visual Studio during a debug session. The GDB command line is shown in the GDB session window.
- A screenshot of the exact error message you get with VisualGDB/VisualKernel.
Hi,
If OpenOCD generally doesn’t work with your hardware, running it with VisualGDB/VisualKernel won’t automatically resolve the OpenOCD issues. If this is the case, please consider asking in the OpenOCD or Raspberry Pi community.
If you can get OpenOCD/gdb working when you launch it manually, we can gladly help you configure VisualGDB/VisualKernel to use this setup for debugging.
Please refer to the following page for a detailed description of MSBuild project files: https://visualgdb.com/documentation/projects/msbuild/
Hi,
In general, ignoring the .vs, .visualgdb and build subdirectories should work for most project types, however you may need to ignore additional file types depending on your project type. You can find the detailed description of different project types and related files here.
If you encounter file types that are not covered by the documentation, feel free to let us know and we will update it accordingly.
Hi,
This looks like a bug in the gdb executable, that is typically triggered by some constructs in the debug symbols. You can try working around it by:
- Using a different gdb executable from an older or newer toolchain.
- Explicitly selecting another DWARF version in gcc settings (e.g. -gdwarf-4).
- Stripping the debug information from the object files you are not intending to debug.
Hi,
Based on the screenshot you attached, you have 2 instances of OpenOCD running simultaneously (one in the terminal and another launched via VisualGDB). This will indeed not work, as they will conflict with each other.
Please make sure you only have one instance at a time.
Hi,
This looks like a question about the ESP-IDF framework and not something specific to VisualGDB. Please consider asking on the Espressif forums instead. Any advice they may suggest will also work with VisualGDB.
Hi,
No problem, we will try to help you. Please try clicking the “show exception details” link and share the stack trace shown, there as long with the VisualGDB build number from the Help->About VisualGDB window.
Thanks for renewing your support.
This error would happen if the project file would be corrupt (e.g. edited manually). The easiest way to troubleshoot it would be to create another similar project from scratch, make sure it builds, an then compare the .vcxproj files one-by-one, specifically the PropertyGroup parts.
If there are too many differences, you can try merging half of them at a time (i.e. replacing the XML tags with the ones from the other file) and reopening the solution to see if it solves the problem.
