support

Forum Replies Created

Viewing 15 posts - 6,511 through 6,525 (of 7,847 total)
  • Author
    Posts
  • in reply to: VisualGDB extremely slow #7753
    support
    Keymaster

    Hi,

    Most likely the connection to your server is slow. Please try switching on the timing analysis mode in the GDB Session window (timer icon) and selecting “All GDB interaction” view. This will show how much time each GDB command takes. If this does not explain the slowness, please let us know which commands are the slowest so that we could advise you further.

    support
    Keymaster

    Hi,

    OK, it looks like VisualGDB is somehow using the obj/local/armeabi-v7a directory for symbols instead of obj/local/arm64-v8a.

    Does the arm64-v8a directory exist? What does the VisualGDB Launcher Output say when you try to debug your project?

    support
    Keymaster

    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.

    support
    Keymaster

    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?

    in reply to: Teensy 3.2 toolchain #7734
    support
    Keymaster

    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.

    in reply to: STM32F10x EXTI problem #7733
    support
    Keymaster

    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.

    support
    Keymaster

    Hi,

    Thanks for the logs. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.652.msi

     

    in reply to: No program to debug. GDBserver exiting. #7722
    support
    Keymaster

    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?

    in reply to: Teensy 3.2 toolchain #7721
    support
    Keymaster

    OK, which of the boards are you using? The one with AVR microcontroller or the ARM Cortex-based one?

    in reply to: CppEngineHost is hanging up frequently #7720
    support
    Keymaster

    Sure. Let us know once you have further information.

    in reply to: Importing new files #7719
    support
    Keymaster

    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?

    support
    Keymaster

    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.

    in reply to: Set per-file build flags? #7708
    support
    Keymaster

    You can modify your makefile as follows to support per-file flags

    1. Modify the file rule templates to include file-specific variables:

    $(CXX) $(CXXFLAGS) $($(basename $(notdir $<))_FLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)

    1. 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”.

    in reply to: Profiling of Intel Edison? #7707
    support
    Keymaster

    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.

    in reply to: What is the STM32 Legacy HAL API? #7698
    support
    Keymaster

    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.

Viewing 15 posts - 6,511 through 6,525 (of 7,847 total)