[support]

Hi,

Sorry for the delayed reply. We have tried reproducing this, however unfortunately could not get the behavior you are describing. Could you confirm that the problem occurs on a clean “Hello, World” project as well? If yes, could you please attach a screenshot of the “Import a folder recursively” window just before you click the “browse” button and the window that appears after you click it?

[support]

Hi,

As this is a fairly rare scenario, VisualGDB doesn’t offer a dedicated GUI setting for it, however the “Advanced Settings” section lets you customize the command line that VisualGDB will use when running the Segger GDB server. Please see the Segger documentation for an option that allows setting the JTAG scan chain position and explicitly add it to the command line in VisualGDB settings. If  you are not sure, please double-check it with Segger support, as they have a better knowledge of the Segger gdb stub internals.

Once you add the extra command line flag, you will still be able to use the regular VisualGDB settings (e.g. debug interface or FLASH programming mode).

[support]

Hi,

If we ever decided to retire VisualGDB, we would simply publish a DRM-free version that would not depend on our activation servers, just like Adobe did with the old Photoshop releases. However this isn’t going to happen in any foreseeable future – instead VisualGDB is actively growing and reaching out to new communities – the recently added advanced ESP-IDF project subsystem, the upcoming J-Trace and Arduino support, the planned improvements to the custom action subsystem and many more…

[support]

Hi,

Our regular support form will do.

[support]

Hi,

Thanks for sharing this. We haven’t tried OpenCV 3.4.1 yet, so it’s hard to say why it would use absolute paths, but we are planning to update our tutorial soon (also to show the new Advanced CMake project subsystem), so we will recheck this and include a 100% reliable workaround.

[support]

Hi,

This is likely our bug, however unfortunately it’s almost impossible to pinpoint it based on the message alone. Would you be able to attach a repro project so that we could investigate this further?

[support]

Hi,

Thanks for checking this. Looks like the only reasonable way to prevent OpenOCD from erasing those sectors would be to patch its source code. Another option would be to try Segger J-Link. Unlike the community-maintained OpenOCD, their gdb stub is covered by their support, so unless they already have an option for selective erase, they might be able to add it for you.

[support]

Hi,

Please enable verbose output via Tools->Options->VisualGDB and build the project. Then rename/delete one of the files and check the build output for the “Checking for previously transferred files that no longer exist…” line. If it is present in the build log, please let us know the subsequent lines. If not, please double-check that the .vgdbsettings file sets DeleteDisappearedFiles to true.

Also you can reproduce it on a basic “Hello, world” project, you can simply send it to us and we will investigate it on our side.

[support]

Hi,

VisualGDB would normally remember the USB serial number of the ST-Link you selected in the wizard/project properties and automatically select it next time. It will only show the selection dialog if more than 1 ST-Link is found and none of the found instances has a matching serial number.

If you want to select a specific ST-Link instance, simply pick it on the Debug Settings page of VisualGDB Project Properties (or manually change the serial number stored in the .vgdbsettings file to an invalid value to trigger the selection dialog).

[support]

Hi,

Sorry, not yet. We have done preliminary research and will include this in v5.4, but it isn’t available in Preview 1 yet (and likely won’t be included in Preview 2 that will be focused on J-Trace support).

[support]

Hi,

VisualGDB offers a much more streamlined experience than the regular VS2017 Linux integration. First of all, it uses a highly optimized build backend that works much faster for large projects with complex structure, and is generally more reliable.

Second of all, VisualGDB provides known workarounds for common issues on the underlying Linux tools. Inaccurate path mappings, missing LD_LIBRARY_PATH entries, mismatching interactive/non-interactive environments and many other scenarios. VisualGDB can automatically discover and fix many issues that would normally take hours to diagnose.

Our debug engine is also designed to recover from known gdb bugs and provides deep diagnostic tools (e.g. a tool for analyzing timings of specific underlying commands that help reduce latency on slow connections).

On top of that VisualGDB offers a Clang-based IntelliSense engine that is specifically designed to handle Linux-specific code and provides many C#-like features: detailed code map, create-from-use, etc.

VisualGDB also includes very deep integration with Make, CMake and Qmake that let you use convenient GUI to quickly edit various project settings without the need to understand the specifics of the project file formats. Our Advanced CMake project subsystem brings this even further – it lets you use the regular Solution Explorer GUI to view and edit CMake targets, automatically editing CMakeLists.txt files in response.

Beyond the regular editing and debugging functionality, VisualGDB includes advanced valgrind-based profiler optimized for huge projects, support for running unit tests on Linux machines (with code coverage), static and dynamic code analysis tools and a convenient set of custom actions that lets you easily transfer files between machines as a part of build or while preparing for debugging.

There are also numerous customization options (like using a custom command for sending the ‘break in’ signal to your app if your Linux distro is configured to ignore the regular SIGINT mechanism) that come in handy when dealing with highly customized target environments and features like Team Settings that help you share common settings to other team members instead of painstakingly setting them up on each machine manually.

You can get a quick overview of the Linux-related highlights here or browse through our Linux tutorials here.

Hope this explains. If you have any further questions, feel free to share them and we will be happy to answer them.

[support]

Hi,

Yes, we indeed ship the pre-built recent versions of the GNU tools like GCC and GDB, however unfortunately resolving the internal bugs of those tools is beyond what we can offer. Hence our best advice for this type of problems (if you run into it again and cannot resolve it via compiler settings) would be to downgrade to a previous gdb release until we release another pre-built version based on newer sources.

You can always download the older toolchain versions here: http://gnutoolchains.com/arm-eabi/

Simply copy the arm-eabi-gdb.exe executable from an older toolchain to the newer one and you will be able to use the newest toolchain (including all optimization features it offers) with the old gdb debugger.

 

[support]

Hi,

Thanks for sharing the log. This looks like an internal bug of the gdb debugger included in your toolchain. Please try using a different gdb version (e.g. from an older toolchain), or try changing the debug information format in your project properties as this might stop the bug from being triggered.

[support]

Hi,

Strange, the log doesn’t indicate any known error. As a quick check, does restarting your computer solve the problem?

[support]

Hi,

Thanks, we have reproduced it and fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2127.msi

 

[Author]

Posts