support

Forum Replies Created

Viewing 15 posts - 1,561 through 1,575 (of 7,989 total)
  • Author
    Posts
  • support
    Keymaster

    Hi,

    This looks like your VisualGDB installation is corrupt. Please make sure you are using an unmodified installer and do not edit any files or registry entries.

    If nothing helps, please attach a screenshot of the Help->About VisualGDB window.

    in reply to: Command line rebuild ignores -Wall #30842
    support
    Keymaster

    Thanks, this is a different issue. When using the VisualGDB.exe /build or /rebuild command for Advanced CMake projects, it was not properly passing the build type to CMake, so it ended up building the debug configuration (despite using the release folder).

    We have fixed it in this build: VisualGDB-5.6.3.4195.msi

    We also recommend building Advanced CMake projects by dumping the build/configuration command lines to batch files as shown here.

    in reply to: Live stack monitor for GCC Projects? #30841
    support
    Keymaster

    Please double-check the values of __StackLimit  and __StackTop  per our previous reply.

    in reply to: Command line rebuild ignores -Wall #30839
    support
    Keymaster

    Hi,

    If you believe VisualGDB is working incorrectly, please provide complete unambiguous steps to reproduce the problem from scratch. The steps should start with creating a new project, and should either mention every involved setting, or include screenshots of every involved wizard/settings page and every other change. They should also include any relevant logs.

    Please see our problem reporting guidelines for more details.

    in reply to: Command line rebuild ignores -Wall #30837
    support
    Keymaster

    Hi,

    This is by design. Unless you do a full rebuild, the build system only builds the files that are out-of-date (i.e. the sources have changed more recently than the objects). Files that are up-to-date are not rebuilt and the warnings that were shown during their compilation will not be shown again unless these files become out-of-date again. This is standard behavior for all build systems we are aware of and is not specific to VisualGDB.

    in reply to: Visualgdb Make exception #30836
    support
    Keymaster

    Hi,

    This looks like an internal error in GNU Make itself. The easiest workaround would be to switch to a different project type that does not use Make (e.g. MSBuild or CMake + Ninja).

    in reply to: MSP430 programming without mass erase #30825
    support
    Keymaster

    Hi,

    The MSP430 support in VisualGDB is implemented via an open-source tool called msp430-gdbproxy. Although it currently only supports erasing the entire FLASH memory, you can easily modify it to erase a custom range instead.

    You would need to clone the msp430-gdbproxy repository and edit the MSP430Target.cpp file to support an additional command (e.g. “erase_range”). Then you can remove the original “erase” command from the <sysgcc>\msp430\msp430-bsp\debuggers\core\edp.xml file and add a custom “erase_range” command to VisualGDB Project Properties -> Additional GDB Commands.

    in reply to: Building VisualGDB project with MSBuild #30815
    support
    Keymaster

    No worries and good to know it works. We have updated our documentation to explain the color coding of exportable command lines to avoid any further confusion.

    in reply to: Building VisualGDB project with MSBuild #30808
    support
    Keymaster

    Yes, clicking on “Dump command line to Batch File” should open a dialog asking for the location of the .bat file. If this doesn’t happen, please try attaching a screenshot of the build window showing the context menu with the “Dump command line to Batch File” option.

    in reply to: Live stack monitor for GCC Projects? #30806
    support
    Keymaster

    Hi,

    VisualGDB should normally fill the stack automatically as long as you enable the option in Embedded Debug Tweaking.

    Once a breakpoint in main() is hit, it will try to find one of the following symbols in the order shown below: __StackLimit, end ,_ebss, _edata.  Then, it will fill the area between the first found symbol and the current value of $sp, and will begin monitoring it. The __StackTop or _estack symbol will be used to determine the total stack size.

    BTW, the stack monitoring logic is implemented in our open-source Live Watch plugin, so you can always tweak it if you would like to support special project layouts.

    in reply to: ESP32 C3 support #30805
    support
    Keymaster

    Hi,

    VisualGDB 5.6 Beta 3 already supports it, as long as you our latest ESP32 toolchain, ESP-IDF 4.3 and the most recent OpenOCD package.

    support
    Keymaster

    Sorry for confusion. If OpenOCD is running on a Linux machine, indeed the “dump_image” command with a Windows path won’t work.

    The easiest way to get it working would be to port the mbatch command from our OpenOCD fork (see this commit). You may need to adjust the code slightly, since the interfaces used by OpenOCD to implement custom commands change from version to version. You can use this fork as a reference. Once VisualGDB detects that OpenOCD supports the mbatch command, it will keep using it instead of dump_image.

    in reply to: Why don't the tutorials work?? ESP_ADF #30796
    support
    Keymaster

    Please follow the tutorials.

    in reply to: Why don't the tutorials work?? ESP_ADF #30793
    support
    Keymaster

    Hi,

    We have just rechecked the latest ESP-ADF framework. Just as our tutorial mentions, it doesn’t work with the latest GCC 8.x, but does work if you install GCC 5.2.0. This happens because ESP-ADF is based on an older ESP-IDF, that expects that specific old compiler version. Most likely, you ended up using GCC 5.2.0 with VS Code and GCC 8.x with VisualGDB.

    Please double-check your GCC versions in the toolchain selection drop-down and make sure you are using GCC 5.2.0 with ESP-ADF as explained in the tutorial.

    in reply to: live tracing is not #30792
    support
    Keymaster

    Hi,

    As you have never provided the complete non-ambiguous steps to reproduce the problem from scratch, all we could do is re-run our standard coverage tests on a STM32CubeMX project during the v5.6 Beta 3 release cycle. They did uncover a glitch that could be causing this issue and we have fixed it in the Beta 3. Please try downloading and installing it from the download page.

Viewing 15 posts - 1,561 through 1,575 (of 7,989 total)