Forum Replies Created
-
Posts
-
Hi,
Yes, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.656.msi
If it does not work, please send us the contents of the %LOCALAPPDATA%\VisualGDB\AndroidBinaryCache folder so that we can try reproducing the problem locally.
Hi,
Strange. The log looks like the gdb included in the Android NDK itself does not support your device. Can you check the VisualGDB Launcher Output for the path of the GDB executable? Perhaps VisualGDB is launching an incorrect version of gdb?
Then you can simply use our ARM toolchain. You can combine our legacy device tutorial with the tutorial you mentioned to enter the correct settings into VisualGDB.
We have also added Teensy boards to our watch list, so if their popularity continues to grow, we will add direct support for some of them.
Hi,
Looks like you are missing an interrupt handler for some of the interrupts. Please define the DEBUG_DEFAULT_INTERRUPT_HANDLERS macro in VisualGDB Project Properties and try running your program again. You should then see which exact handler is missing.
Hi,
Thanks for the logs. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.652.msi
Hi,
VisualGDB always runs chmod +x on the deployed files. Perhaps some permissions problem is preventing it from working properly? Are you connecting to your device as root?
OK, which of the boards are you using? The one with AVR microcontroller or the ARM Cortex-based one?
Hi,
Normal VC++ projects don’t automatically add files from the file system and VisualGDB is trying to follow that behavior.
We could add a command to rescan the files and update the project similarly to the Import Directory Recursive command. Would that be helpful?
Hi,
Please try the following build:http://sysprogs.com/files/tmp/VisualGDB-5.1.4.650.msi
Then open a VisualGDB project, launch the toolchain testing and send us the contents of the VisualGDB Launcher Output view from the Output window. It should contain detailed log messages explaining the gdbserver location logic.You can modify your makefile as follows to support per-file flags
- Modify the file rule templates to include file-specific variables:
$(CXX) $(CXXFLAGS) $($(basename $(notdir $<))_FLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)
- Add file-specific flags defines above the FileSpecificTemplates line:
LEDBlink_FLAGS := -O0
You can modify the $(basename $(notdir …)) expression to use the directory name instead of the file name. See the GNU Make function reference for more details.
You can similarly add the “include” lines to the Makefile to include your own files containing lines like “CFLAGS += some_flag”.
Hi,
As of v5.1, VisualGDB only supports profiling for barebone targets like STM32. We do consider adding Linux support in the future versions. We will announce through our Twitter once it is available.
Hi,
The checkbox results in defining the USE_HAL_LEGACY macro that enables some backward compatibility features in the HAL headers. You can search for the macro in the HAL headers and sources to see which exact functionality is affected.
Hi,
You can replace the CppEngineCore.dll file with a debug build from http://sysprogs.com/files/tmp/CppEngineCore.dll, create a dump file via Task Manager and send it to us. This way we should be able to see what is causing the crashes and fix them.
