esp8266 arduino : gdbstub not supported anymore ?

Sysprogs forums Forums VisualGDB esp8266 arduino : gdbstub not supported anymore ?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #24487
    christophe
    Participant

    Hi,

    I’m trying to rebuild some arduino projects on ESP8266. Ii seems that the gdbstub debugging method is not supported anymore ?

    I receive this error : error : ‘gdbstub_init’ was not declared in this scope. And after checking the <GDBStub.h> header file, it is empty.

     

    Info on the build configuration

    NodeMCE 1.0 device

    VS2017

    VisualGDB 5.4R4

    Regards,

    Christophe

    #24501
    support
    Keymaster

    Thanks for linking your forum profile to your key. The GDB stub functionality has actually been greatly improved in the ESP8266 2.5.0 core (in the previous versions it was barely usable), however due to some changes to the internal layout, you would need to install VisualGDB 5.4R3 or later (we recommend the latest R4) and ensure you have the latest ESP8266 Arduino core and the latest ESP8266 debug package installed (you can install both via Tools->VisualGDB->Manage VisualGDB Packages).

    Then try creating a new Arduino project and ensure you can build and debug it (VisualGDB will set the GDBSTUB_BREAK_ON_INIT=1 variable via VisualGDB Project Properties). Then, simply copy the gdb stub-related code from that project to your project and you should be able to use it.

    If gdbstub.h file is empty, it might have been simply corrupted by something else. Deleting and reinstalling the component providing it (if you are not sure, please let us know the full path to that file) should normally resolve it.

    If you are not using Arduino, please let us know the exact toolchain and project type you are using (MSBuild, Make, or the new RTOS SDK 3.0 that comes with its own build system) and we will help you get it to work.

    #24526
    christophe
    Participant

    Hi,

    Thanks,  I’ve updated to the latest 2.5.0 Core, but still fails. So, i removed all packages and re-download them, and now, it is working fine. As you said, something was broken somewhere.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.