Forum Replies Created
-
Posts
-
Hi,
No worries, good to know you got it to work. If you encounter any further problems, feel free to start another topic.
Hi,
According to our records, your technical support as expired. Please renew it via https://sysprogs.com/splm/mykey and we will be happy to help you.
Hi,
Yes, this is a known limitation of Linux systems, although it’s very well-known and relatively well-documented, so as long as you can find someone with basic Linux knowledge, they should be able to figure it out quickly.
Hi,
The problem could also be caused by Visual Studio having some files in the toolchain folder open (e.g. the debugging plugin).
Please try updating to Preview 8 (your log mentions version 5.3.6 that is Preview 6). It includes a better toolchain updating mechanism that first removes the previous toolchain folder and only then installs the new toolchain.
Hi,
Please try searching the library files (.so) for the ones defining the missing symbols. Then ensure that the linker can find them.
Sometimes the .so files contain a link to another file instead of the actual library (you can see this in text editor). If this is the case for the .so file containing the missing symbols, please ensure that the target linked from the original .so file exists. If it’s using syntax like /usr/lib/… please replace it with =/usr/lib/… so that the linker can automatically substitute sysroot.
Hi,
If your program uses X11, the ‘sudo’ command won’t automatically forward the X11 connections. The easiest way around it would be to create a new ‘root’ connection to your Linux machine (instead of the current user name). You may need to enable root logins explicitly in your sshd configuration (check your Linux distro manual for specific steps to do that).
Hi,
Thanks for checking this. It looks like your antivirus might be preventing VisualGDB from running the downloaded executable. Please try disabling it and updating the toolchain again.
Hi,
We are planning to update our STM32 package in the next 1-2 months, so the new devices will be supported then. Until then please try following the legacy device tutorial: https://visualgdb.com/tutorials/arm/legacy/
You can also try cloning our STM32 BSP generator and running it on the latest STM32 SDK, however this will likely trigger errors due to changes introduced by ST (we will update the generator as a part of our BSP update process).
Hi,
This could be if your C++11 headers are out-of-sync with the libraries. Please ensure you are using exactly the same target image as our toolchain uses (see http://gnutoolchains.com/raspberry/) and try resynchronizing the sysroot if you install any packages on top of the original installation.
Hi,
Good to know it works. If you ever decide to diagnose this, let us know and we will help you understand why right-click adding does not work.
Hi,
Please use the following option:
Solution Explorer->VisualGDB Project Properties -> Debug Settings->Run debugger as root with sudo.
Hi,
Thanks for the suggestion about showing the variable sizes. We have added it to this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.8.1774.msi
It will show the size once you hover the mouse over a reference to a variable (but not the definition).
We have added support for evaluating ‘==’ to the backlog and will try to include it in the final build of v5.3.
Supporting octal/binary is harder, as it would involve several unreliable hacks on top the VS infrastructure, so our current advice is to use the “print” command in the GDB Session window (e.g. p/o <variable> for octal and p/t <variable> for binary).
You can view the stack pointer value via Debug->Windows->Registers or by adding “$sp” to the Watch window.
Hi,
The answer depends on the error you are getting. Do you still get the “access denied” error? Are you using VisualGDB 5.3 Preview 8? Does you Visual Studio have sufficient access rights (e.g. Administrator access) to write to the toolchain folder?
Hi,
We usually update our STM32 package quarterly, so we will most likely officially support it within the next 2 months.
If you want to create a project manually before we fully support the device, please follow this tutorial: https://visualgdb.com/tutorials/arm/legacy/
Hi,
This should normally work. Please try adding the variable manually by typing “flag” in the Live Variables window instead of using the right-click. If you still get the “echo” error, please try renaming the variable to something unique. As VisualGDB always expands the preprocessor macros in the Live Variables, it could accidentally expand a macro with the same name that would resolve to an invalid name like “echo”.
