By default Eclipse saves debug configurations in its workspace directory, not in the project directory, so this file does not get committed into version control. Since it is a minor pain to set up GDB Hardware Debugging, I recommend to improve instructions as follows:
In instructions of how to debug in Eclipse using OpenOCD and GDB Hardware Debugging, here:
https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-eclipse
Before step 12, while still in the Debug Configurations setup dialog, go to the last tab ("Common") and select the radio button for "Shared file." This is because Eclipse by default chooses "Local file" which places the debug configuration in the Eclipse workspace directory. By choosing "Shared file" the file will be placed in the project directory, allowing it to be committed into version control.
By default Eclipse saves debug configurations in its workspace directory, not in the project directory, so this file does not get committed into version control. Since it is a minor pain to set up GDB Hardware Debugging, I recommend to improve instructions as follows:
In instructions of how to debug in Eclipse using OpenOCD and GDB Hardware Debugging, here:
https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-eclipse
Before step 12, while still in the Debug Configurations setup dialog, go to the last tab ("Common") and select the radio button for "Shared file." This is because Eclipse by default chooses "Local file" which places the debug configuration in the Eclipse workspace directory. By choosing "Shared file" the file will be placed in the project directory, allowing it to be committed into version control.