Forum Replies Created
-
Posts
-
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”.
Hi,
Thanks for confirming this. It could be caused by incompletely downloaded header directories. Please try refreshing them via the IntelliSense Settings page of VisualGDB Project Properties.
Hi,
Yes, VisualGDB-5.3.7.1769.msi is newer than 5.2R9 (we actually recommend downloading v5.3 Preview 8 as it is even newer than build 1769).
Hi,
Please try updating to VisualGDB 5.3 Preview 8 and installing the latest ESP32 toolchain. It includes a FLASH programming mechanism provided by Espressif that might be more tolerant to non-typical configurations (our FLASH programming algorithm was based on undocumented API). If it doesn’t work either, please attach both OpenOCD logs and the full gdb log to see which exact command fails and what error is related to the failing command.
Hi,
This looks like a gdb bug actually. Can you confirm that you also get the wrong value when running “print <expression>” manually via the GDB Session window?
Hi,
It looks like you are trying to create a live variable for an expression that is not valid in the current context. Is it a global variable visible from all the source files or a local variable inside a function/method?
Hi,
Please check the OpenOCD window for errors. The GDB log only shows that OpenOCD refused the connection, while the real reason for the error is normally shown in the OpenOCD log.
Hi,
Please try using the “Test OpenOCD Settings” button (or installing VisualGDB 5.3 Preview 7). This should automatically fix the driver issues.
Hi,
Yes, but you would need to contact our support in order to get your previous license deactivated from our side.
Hi,
Thanks for confirming this. This could be caused by IntelliSense and the compiler using different sets of headers or different build parameters. Please let us know the type of the project (Embedded/Linux/Android) and the machine on which it is built (Windows or Linux via SSH). If you could also attach a screenshot of the problem, we might be able to diagnose it by checking for known irregularities.
Hi,
This feature hasn’t been officially announced yet and will be included in the upcoming Preview 8.
In the meanwhile you can try the following build that already includes it: http://sysprogs.com/files/tmp/VisualGDB-5.3.7.1769.msi
