Forum Replies Created
-
Posts
-
Yes, Quick Debug has its own path mappings stored in the .quickdbg files under %LOCALAPPDATA%\VisualGDB\QuickDebugPresets.
You can edit the Quick Debug path mappings using the path mapping icon in the GDB Session window (item #3).
Hi,
No problem, we will be happy to look into this. Would you be able to share a basic project that reproduces both issues? You can either attach it here as a zip file (make sure you delete the built files), or upload it to an external file sharing service.
Thanks, we have updated VisualGDB to fix the issue: VisualGDB-5.5.8.3753.msi
Good to know it works. BTW, if the file uses the SVD format, it should have been imported automatically together with the rest of the SDK. Feel free to share a link to the SDK and we will make sure it gets handled fully automatically next time.
Thanks for confirming your license, we have linked it to your account.
Indeed, VisualGDB internally uses its own format to define the registers. However, it also supports the SVD file format used for modern ARM devices. Normally, if the register file was not automatically imported, you can click the “locate” link in the Hardware Registers window and point VisualGDB to the SVD file, and it will get automatically converted into the VisualGDB format.
The logic for importing the SVD files is open-source and is available here: https://github.com/sysprogs/BSPTools/blob/master/libraries/BSPGenerationTools/SVDParser.cs
If this doesn’t help, please upload the SDK that did not get properly imported to a file sharing service (e.g. DropBox) and post a link there so that we can investigate it further.
Hi,
This looks like a proxy server configuration issue. Please see the following page for a detailed explanation: https://visualgdb.com/documentation/proxy/
Hi,
This is likely by design, as you have not included the header file declaring the function. This will not cause a critical build error, since C99 does support implicit declarations.
You can read more about this warning, and implicit declarations here: https://stackoverflow.com/questions/32703675/implicit-declaration-of-function-enterchar-wimplicit-function-declaration?rq=1
No problem, we have updated the version parsing logic in this build: VisualGDB-5.5.8.3747.msi
OK, as it looks like something very rare and specific, the easiest way to us to narrow it down would be if you could share the exact steps to reproduce it on our side.
Please try creating a new project completely from scratch, make sure the problem still exists, and then share the complete steps we could follow on our side to reproduce it.
Sorry, we thought you were asking about merging the contents of 2 project files.
Merging the functionality of 2 projects is a complex engineering task that requires the understanding of both projects, the underlying software frameworks and its limitations. Hence, it cannot be done automatically.
If you need help with this, please consider contacting our sales and we will give you a quote.
OK, thanks for confirming this. We have rechecked everything again and confirmed the problem.
Turns out, the issue was caused by a recent update on our server that was not yet caught by our integration tests (we run the full set of tests before each preview release, such as v5.5 Preview 5). The daily infrastructure tests run on the latest VS2019 and hence didn’t catch this either.
Sorry for being skeptical about it – we had previously encountered very similar errors caused by client-side antivirus software trying to hijack SSL connections without properly installing new root certificates, and another case where it was caused by broken group policy, so it looked like another instance of that problem. Either way, we have fixed the issue on our server and also updated the infrastructure tests to check for it, so it shouldn’t happen again.
Hi,
Sorry, we don’t have a tutorial on merging multiple projects. Our best advice would be to look through our documentation on project types to understand the type of the project you are using, and where it stores the lists of files and settings.
Then, you can try editing these locations manually to merge the settings from different sources.
If you could let us know the type of the project (per the documentation page), we can share a few pointers, but this will still require non-trivial editing of configuration files, and many need some troubleshooting.
Sorry, we have a large set of integration tests that is run on 32-bit and 64-bit Windows 7 and Windows 10 using VS2008, 2010, 2012, 2013, 2015, 2017 and 2019, and they do not trigger the issue.
It looks like something is broken with a specific laptop, so our best advice would be to reinstall Windows there.
Sorry, we are not sure what you meant. If you are looking for a specific feature, please consider searching our tutorials. They provide detailed step-by-step instructions for most of the features.
If you could still cannot find it, please attach a screenshot explaining what exactly you are looking for, and we will try to help you.
