Forum Replies Created
-
Posts
-
Hi,
No problem. The macro looks like a leftover from a GCC-based project that should not be set for Keil-based projects. If you could let us know the exact steps to reproduce this, we should be able to fix it. Alternatively, removing the macro via VisualGDB Project Properties should work as well.
You can set the VC++ IntelliSense as a default engine via View->Clang IntelliSense Diagnostics Console -> Default Engine.
The difference between debug and release is usually just the optimization. You can find the exact command line options VisualGDB passes to Keil in the .rsp file in the VisualGDB\<Configuration name> subdirectories. If you can reliably reproduce problems with a certain project/configuration, please try building it with uVision and check if the problem persists. If not, please try comparing the command lines from the .rsp files with the command lines from Keil uVision (enable the “create batch file” to make uVision dump the command lines). E.g. try linking the object files produced by uVision using the VisualGDB’s link command line or vice versa.
Hi,
No problem. We have just released VisualGDB 5.4 Beta 1 that includes this fix. You can download it directly here: http://visualgdb.com/download/
Hi,
No problem and thanks for the kind words. If you encounter any further issues, don’t hesitate to create another thread.
Hi,
Thanks for clarifying this. VisualGDB uses original Arduino build tool (arduino-builder) to discover the libraries. This is done to ensure 100% compatibility and interoperability the Arduino IDE and other command-line build tools.
To our best knowledge, arduino-builder does not support referencing a specific version of the library, so the only way to achieve that would be to remove the library from the regular search path and add it to the project-specific search path. Another option would be to just rename the old library (e.g. to ArduinoJsonV5) and rename the header file accordingly. Once you use the new header file name in your sketch, Arduino builder (and VisualGDB) will automatically locate the correct version of it.
Hi,
Yes, sorry for the delay. We originally planned to release the first Beta (with the finalized feature set) last week and the final release a few weeks after, however we got a few interruptions and this got delayed. Currently we are running the final tests on the last feature of v5.4 – the new file/folder synchronization engine for Linux machines. We expect to finish the tests and polish up the remaining rough edges in the few next days and will then release a beta. Depending on the amount of feedback on the Beta, we will publish the final release in the next few weeks following the beta.
Hi,
Thanks for reporting this, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2636.msi
Hi,
Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2635.msi.
When you select your toolchain, please click the “customize” button to the right from the selector and then choose “Run Cygwin Commands: In an interactive bash session”. It will automatically wrap build and debug-related commands the proper invocation of “bash –login”.
Hi,
If you are using the Custom edition or higher, you can configure it via VisualGDB Project Properties -> Raw Terminal. It not, please try using SmarTTY – a free stand-alone equivalent of the VisualGDB’s terminal functionality.
Hi,
Thanks for the detailed log. We have replied per email and will also post a copy here (without any project-specific references) in case anyone else encounters a similar issue.
It looks like the gdb executable you are using indeed reports that the “tu” variable has 0 children:
-var-create --frame 0 --thread 1 - * "tu" ^done,name="var1",numchild="0", <...>
It also looks like you are using a fairly old version of GDB:
GNU gdb (GDB) <...> Copyright (C) 2013 Free Software Foundation, Inc.
Please try building gdb 8.2 from sources (it is usually straight-forward on Linux systems) and try using it with VisualGDB. If this still doesn’t help, please check where the “tu” variable is defined (identify a specific source file and see whether it’s a global variable, local variable, or a static variable) and double-check that the file defining it is built with -ggdb. If this doesn’t help, please try experimenting with the DWARF format switches (e.g. -gdwarf-2).
Hi,
It looks like your Nordic BSP (located in %LOCALAPPDATA%) got corrupt – the gcc_startup_nrf52840.S file should normally be present. Please try reinstalling it via Tools->Options->Manage VisualGDB Packages.
Hi,
Sorry, it’s hard to see the relevant text from the screenshot. Please post the text version so that we could see what is going on.
Hi,
The default library directories are specified via Tools->VisualGDB->Arduino Settings. You can try removing the main directory there and specifying it for each project separately.
If this is not what you are looking for, please provide more details: the layout of your files and the exact outcome you would like to achieve (i.e. which libraries should be used by each project).
Hi,
Arduino build tools automatically discover the libraries inside the search path based on the header files referenced in the sketches. If you would like to use several versions of the same library, please place it outside the regular library search directories and then explicitly add the parent directory of the library to the per-project library search path (first page of VisualGDB Project Properties).
Let us know if you need more details and we will be happy to help.
Hi,
Please try switching the GDB Session window to the “All GDB Interaction mode”, reproduce the problem and then locate the relevant lines from the log. If GDB indeed reports the variable as empty, the source file declaring it might have been built without debugging symbols (-ggdb flag). If this is this case, please check with the library vendor for a debug-enabled version of the library.
Hi,
VisualGDB uses different synchronization logic for different files/directories. E.g. the files in the source directory are only synchronized one way (Windows to Linux). Stepping into a source files that is not normally synchronized will get it temporarily downloaded under %LOCALAPPDATA% (next time you start the debug session, it will be rewritten).
We have also added support for advanced directory synchronization options in the upcoming v5.4 Beta 1. It allows defining arbitrary per-project or per-host directory pairs, setting advanced triggers for synchronization and allows transferring only changed files for both incoming and outgoing transfers. We are currently running the final tests on it and are expecting to release it in a few more days. Please consider waiting until we release it, as it might considerably simplify your setup.
