Forum Replies Created
-
Posts
-
No problem, we will try to explain what is going on.
The problem is most likely related to the TLS versions (protocol used by HTTPS). In order to maintain backward compatibility with VS2008, VisualGDB binaries are built to be compatible with all .Net versions starting from 3.5. However, the actual .Net 3.5 requires the old TLS 1.1 protocol that has been dropped by the latest web server software.
So, as a workaround, VisualGDB uses configuration files (e.g. VisualGDB.exe.config) to explictly request Windows to prefer the newer .Net 4.0 that works with the latest TLS:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0.30319"/> <supportedRuntime version="v2.0.50727"/> </startup> </configuration>
The error would happen if you were using the old VS2008 (that depends on .Net 3.5) or somehow Windows would stop using the latest .Net version and would revert to 3.5. It is difficult to say why exactly it would happen on a particular machine, however we can suggest a few workarounds:
- Try replacing the SessionServer.exe executable in the VisualGDB directory with this version: https://sysprogs.com/files/tmp/SessionServer.exe
- Double-check that the visualgdb.exe.config and SessionServer.exe.config files are present and specify v4.0 before v2.0.
If nothing helps, you can work around it by using a separate forwarder that would fetch the session keys using TLS 1.2 and feed them to VisualGDB. Let us know if you nothing else helps, and we will provide more details.
It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey
Update: it looks like you are using a floating license. Please try selecting Help->About VisualGDB->Revert to trial. If this fixes the problem, it will be covered by our support even with an otherwise expired support period.
Well, yes and no. As far as VS code goes, the answer is still a hard no. VS Code is rather limiting in terms of GUI integration, so supporting it would mean competing against a plethora of free alternatives, while being largely limited by the VS code framework, and hence not being much better.
If you know any successful paid extensions to VS Code, it would be interesting to have a look, but if there aren’t many of them, it somewhat proves our point.
The good news is that the cross-platform GUI frameworks have finally caught up, so we have been working on our own cross-platform shell, that supports Windows, Linux and Mac, while being built mostly on the same tech stack as VisualGDB. It will first come out as a separate product focused on a few AI-specific tasks, and will then start gradually receiving functionality from VisualGDB. Stay tuned, the first preview build of the new product is a couple of weeks away!
Sorry for the delay. We have rechecked the logic behind BSP_SOURCE, BSP_EXPLICIT_LOCATION and loading of the regular BSPs, and it looks like the regular BSP loading is not necessary when either one is set:
if((NOT ("${BSP_EXPLICIT_LOCATION}" STREQUAL "")) OR (NOT ("${BSP_SOURCE}" STREQUAL "")) ) set(_load_regular_bsps 0) endif()We have updated the code on our side and will include it in the next VisualGDB update after it passes all tests.
Thanks for confirming your license.
You can find a tutorial on custom actions here: https://visualgdb.com/tutorials/custom/steps/. The tutorial is rather old, but the concept of custom actions hasn’t changed since it was published.
It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey
Hi,
This could be a bug in the gdb, or some quirks of the build system that might be solvable with path substitutions, but you would need to understand what path format would work with the underlying debugger.
We would advise first getting a simple breakpoint to work by running gdb manually and experimenting with different path formats. Once this works, configuring VisualGDB to use the same path syntax should be straight-forward. If not, let us know the path format that works manually, and we will help you configure VisualGDB to use it.
@bflannery, yes and thanks for pointing it out. There is a bug in VS that sometimes stores the wrong colors, although it happens very rarely, so we could never fully reproduce it.
We have a page describing it here: https://visualgdb.com/documentation/colors/
It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey
We have to follow the market demand. We will initially offer both versions side-by-side, and will then decide based on the amount of users interested in each one.
Sorry, based on what we see, you do not have a valid license and tried tampering with the activation system. We will not be able to help you.
Sorry, based on what we see, you do not have a valid license and tried tampering with the activation system. We will not be able to help you.
VisualKernel is a much more niche product that VisualGDB. It solves a narrow subset of problems that are relevant to a smaller number of users, hence it is not updated as regularly.
Based on the feedback we receive, many users would appreciate a direct way to run VisualKernel on Linux and not have to install Windows + Visual Studio in a virtual machine.
We are working on a technology that will allow doing that, while retaining all advanced features (e.g. tracing). It will be first integrated into VisualGDB and another brand-new cross-platform product, and will then make its way into VisualKernel. Until then, we are not planning to do any major VisualKernel updates.
Please refer to the following thread: https://sysprogs.com/w/forums/topic/visualgdb-ui-refresh/
VisualGDB is already integrated into the Visual Studio theming engine. It picks up colors for common controls to match what Visual Studio itself uses, and follows the dark/light themes. Hence, when the new UI is selected, most of the VisualGDB controls should automatically pick up most of the new colors. We will then monitor the popularity of the new GUI, and will gradually resolve the remaining inconsistencies over future releases.
As for redesigning all of our GUI using a new design system, it would not be very practical, as our users would rather prefer new functionality and compatibility with the latest devices, than a lengthy redesign bringing no new functionality, while delaying functional improvements.
