Forum Replies Created
-
Posts
-
Sorry, this looks like a very niche configuration that will not be supported directly. If you could find out the exact steps and command lines to do it outside VisualGDB, we can help you configure VisualGDB to automate them, but unfortunately we cannot offer any help beyond that.
No problem. VisualGDB would create a library project when it detects that the original IAR project was a static library. The check is done using the “GOutputBinary” element in the IAR project file.
Most likely, your project was created using an older version of IAR and our importing plugin doesn’t handle it properly. If you could attach the .ewp file here (or send it via our support form), we will be happy to update our importer to handle it properly. You don’t need to share any actual source code.
If you do not want to share the project file, you can also patch the IAR project importer on your side by cloning it from Github: https://github.com/sysprogs/BSPTools/tree/master/ProjectImporters/IARProjectImporter
Hi,
Based on the log, it looks like the toolchain got imported as an embedded, not Linux toolchain. Could you please share the screenshots of how exactly you import it (including all relevant wizard pages), so that we could double-check what is going on?
Hi,
It looks like you are trying to debug a static library:
&"\"C:\\Users\\Public\\Projects\\ProvaErmesGDB\\VisualGDB\\Release\\ProvaErmesGDB.a\": not in executable format: File format not recognized\n"Please note that static libraries cannot be programmed or debugged directly. Instead, they need to be linked into an executable project, that could be programmed and debugged as expected.
You can switch between building a static library and an executable via VS Project Properties -> Configuration -> General (see this page for a detailed description of MSBuild property types).
No problem, please try this build: VisualGDB-5.5.4.3559.msi
It will automatically detect the old Windows 10 builds and will revert to using the old bash.exe syntax when targeting WSL.
Sorry, this looks like a generic C++ question and is outside of the VisualGDB support scope. For generic programming questions please consider sites like StackOverflow.
No problem. Please try updating to VisualGDB 5.5 Preview 4. If the problem persists, please share the updated exception log and we will investigate it further.
Generally, network configuration is outside of VisualGDB’s control and hence the help we can provide here is very limited.
If you are comfortable configuring the VPN, we would advise setting up OpenVPN on one of the machines, and joining the other one to it. If not, please consider using one of the cloud-based VPN services, and connecting both computers to that VPN. This would have the same effect as physically putting them on the same network.
It might theoretically work, however this is not something we have explicitly tested (or can officially support). When the control passes from the bootloader to the main application, the variable would get rewritten by the initialization code, and that may trigger weird bugs.
Either way, it could be worth trying. The variable name is s_FastSemihostingState in FastSemihosting.cpp. If it doesn’t work, making some sort of a syscall mechanism between the bootloader and the main application could be a better option.
Hi,
No problem, we have published a detailed tutorial here: https://visualgdb.com/tutorials/arm/remote/
According to our records, your support period has expired. Hence, we are not able to offer any further technical support, sorry.
Thanks for sending the logs to our support email. It looks like you are trying to debug a static library:
C:\Program Files (x86)\Sysprogs\VisualGDB\Keil\arm-eabi-gdb.exe --interpreter mi "C:\Users\amali\Documents\VS_prosject\VisualDGB_5\Test_VGDB_5_IAR_nr2\VisualGDB\Debug\Test_VGDB_5_IAR_nr2.a"
Please note that static libraries cannot be debugged directly. They must be linked with the executable projects, that can be actually debugged. Please double-check that the project you are importing is an executable project, not a static library.
You can check the project type for a VisualGDB project via Configuration Properties -> General page of VS Project Properties (see this page).
No worries. BTW, we have officially released Analyzer2Go 2.1 that includes this fix, adds support for 5 more STM32 boards, and introduces a few more features.
You can read more about it here: https://sysprogs.com/w/analyzer2go-2-1-is-out/
You can find an overview of various VisualGDB editions and their features at the following page: https://visualgdb.com/buy/
