You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard debug configuration using OpenOCD does not work (that's another defect). One of the things that is requested when reporting a gdb / debug failure is a log file from OpenOCD. I added logging information (-l openocd.log -d2) to OpenOCD config options and ran the debug configuration. I got a log from OpenOCD, but could not get a log from gdb. Closer examination proved that gdb was not launched.
To Reproduce
Steps to reproduce the behavior:
Start with a fresh "ESP-IDF GDB OpenOCD Debugging Configuration (in Debug Configurations)
Add -l openocd.log -d2 to the beginning of OpenOCD Setup / Config options.
Add set remotelogfile gdb.log to the first line of GDB Client Setup / Commands text box.
Run the configuration
Since logging is going to a file, there will be no console output.
Wait for the timeout.
Note that there is a "openocd.log" file, but there is no "gdb.log" file.
Expected behavior
I expect that both OpenOCD and gdb will be launched.
The text was updated successfully, but these errors were encountered:
a7v7
changed the title
Espressif-IDE 3.0.0 if loggin is enabled on openocd, gdb will not launch
Espressif-IDE 3.0.0 if OpenOCD logging is enabled, gdb will not launch
Jun 27, 2024
github-actionsbot
changed the title
Espressif-IDE 3.0.0 if OpenOCD logging is enabled, gdb will not launch
Espressif-IDE 3.0.0 if OpenOCD logging is enabled, gdb will not launch (IEP-1282)
Jun 27, 2024
Describe the bug
OS: Win11
ESP-IDF: 5.2.2
Espressif-IDE: 3.0.0
Target: ESP32-S3-DevKitC1-1 (ESP32-S3-WROOM-2 module)
The standard debug configuration using OpenOCD does not work (that's another defect). One of the things that is requested when reporting a gdb / debug failure is a log file from OpenOCD. I added logging information (-l openocd.log -d2) to OpenOCD config options and ran the debug configuration. I got a log from OpenOCD, but could not get a log from gdb. Closer examination proved that gdb was not launched.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect that both OpenOCD and gdb will be launched.
The text was updated successfully, but these errors were encountered: