Unable to start debug session. Error: Failed to launch GDG: .pioinit:12 Error in sourced command file

Good morning,

I use a development platform based on an ESP-PROG and an ESP32 D1 Mini card, and VSCODE +platformio. This environment works well and I was able to try my hand at debugging with a simple program like Hello_World or a bit more complicated. While the program runs fine in relase mode, I am unable to initiate a debugging session with the wif_prof_mgr provisioning sample. The error code is:
Failed to launch GDG: .pioinit:12 Error in sourced command file: Protocol error with Rcmd (from interpreter-exec console “source .pioinit”). Below is the trace of the launch of a debugging session.
Please can you provide me with a clue to solve this problem. I specify that I am new to OpenOCD and GDB.

==============================================================
undefinedC:\Users\XXXX\.platformio\packages\toolchain-xtensa-esp32\bin\xtensa-esp32-elf-gdb.exe: warning: Couldn't determine a path for the index cache directory.
Reading symbols from D:\ESP32_PROJETS\pio_prov\.pio\build\wemos_d1_mini32\firmware.elf...
PlatformIO Unified Debugger -> https://bit.ly/pio-debug
PlatformIO: debug_tool = esp-prog
PlatformIO: Initializing remote target...
Open On-Chip Debugger  v0.11.0-esp32-20220706 (2022-07-06-15:48)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

WARNING: boards/esp-wroom-32.cfg is deprecated, and may be removed in a future release.
adapter speed: 5000 kHz

Info : tcl server disabled
Info : telnet server disabled
Info : clock speed 5000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : [esp32.cpu0] Target halted, PC=0x40088784, debug_reason=00000000
Info : [esp32.cpu1] Target halted, PC=0x40000400, debug_reason=00000000
Info : starting gdb server for esp32.cpu0 on pipe
Info : accepting 'gdb' connection from pipe
Warn : No symbols for FreeRTOS!
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Set GDB target to 'esp32.cpu0'
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 157 KB
Info : Flash mapping 1: 0x40020 -> 0x400d0020, 600 KB
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Auto-detected flash bank 'esp32.cpu0.flash' size 4096 KB
Info : Using flash bank 'esp32.cpu0.flash' size 4096 KB
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 157 KB
Info : Flash mapping 1: 0x40020 -> 0x400d0020, 600 KB
Info : Using flash bank 'esp32.cpu0.irom' size 604 KB
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 157 KB
Info : Flash mapping 1: 0x40020 -> 0x400d0020, 600 KB
Info : Using flash bank 'esp32.cpu0.drom' size 160 KB
Info : New GDB Connection: 1, Target esp32.cpu0, state: halted
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1001 ms). Workaround: increase "set remotetimeout" in GDB
esp_cpu_compare_and_set (addr=0x3ffc08cc <s_phy_int_mux>, compare_value=1074341400, new_value=3007315967) at C:\Users\XXXX\.platformio\packages\framework-espidf\components\esp_hw_support\cpu.c:628
628	{
Warn : esp_symbols table size (0) is not valid!
Error: FreeRTOS: uxTopUsedPriority is not defined, consult the OpenOCD manual for a work-around!
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : [esp32.cpu0] requesting target halt and executing a soft reset
[esp32.cpu0] requesting target halt and executing a soft reset
Info : [esp32.cpu0] Debug controller was reset.
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu0] Target halted, PC=0x500000CF, debug_reason=00000000
[esp32.cpu0] Debug controller was reset.
[esp32.cpu0] Core was reset.
[esp32.cpu0] Target halted, PC=0x500000CF, debug_reason=00000000
Info : [esp32.cpu1] requesting target halt and executing a soft reset
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu0] Target halted, PC=0x40000400, debug_reason=00000000
[esp32.cpu1] requesting target halt and executing a soft reset
Info : [esp32.cpu1] Debug controller was reset.
[esp32.cpu0] Core was reset.
Info : [esp32.cpu1] Core was reset.
[esp32.cpu0] Target halted, PC=0x40000400, debug_reason=00000000
[esp32.cpu1] Debug controller was reset.
[esp32.cpu1] Core was reset.
Info : [esp32.cpu1] Target halted, PC=0x40000400, debug_reason=00000000
[esp32.cpu1] Target halted, PC=0x40000400, debug_reason=00000000
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 157 KB
Info : Flash mapping 1: 0x40020 -> 0x400d0020, 600 KB
[esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Flash mapping 0: 0x10020 -> 0x3f400020, 157 KB
Flash mapping 1: 0x40020 -> 0x400d0020, 600 KB
Info : [esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Info : Auto-detected flash bank 'esp32.cpu1.flash' size 4096 KB
Info : Using flash bank 'esp32.cpu1.flash' size 4096 KB
[esp32.cpu0] Target halted, PC=0x40092612, debug_reason=00000001
Auto-detected flash bank 'esp32.cpu1.flash' size 4096 KB
Using flash bank 'esp32.cpu1.flash' size 4096 KB
** Programming Started **
** Programming Started **
Error: timed out while waiting for target halted
timed out while waiting for target halted
Info : [esp32.cpu0] Target halted, PC=0x40088797, debug_reason=00000000
Error: xtensa_wait_algorithm: not halted 0, pc 0x40088797, ps 0x60023
Error: Failed to wait algorithm (-302)!
Error: Algorithm run failed (-302)!
[esp32.cpu0] Target halted, PC=0x40088797, debug_reason=00000000
xtensa_wait_algorithm: not halted 0, pc 0x40088797, ps 0x60023
Failed to wait algorithm (-302)!
Algorithm run failed (-302)!
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Info : PROF: Erased 28672 bytes in 95.067 ms
Target is already running an algorithm
Failed to start algorithm (-4)!
PROF: Erased 28672 bytes in 95.067 ms
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Info : PROF: Wrote 28672 bytes in 95.044 ms (data transfer time included)
Target is already running an algorithm
Failed to start algorithm (-4)!
PROF: Wrote 28672 bytes in 95.044 ms (data transfer time included)
** Programming Finished in 40798 ms **
** Verify Started **
** Programming Finished in 40798 ms **
** Verify Started **
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Info : PROF: Flash verified in 94.199 ms
Error: **** Verification failure! ****
Error: target_hash 000...000
Error: file_hash: d223e...83fe82
Target is already running an algorithm
Failed to start algorithm (-4)!
PROF: Flash verified in 94.199 ms
**** Verification failure! ****
target_hash 000...000
file_hash: d223e...83fe82
** Verify Failed **
.pioinit:12: Error in sourced command file:
Protocol error with Rcmd
==============================================================

1 - What does this message mean:
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1001 ms). Workaround: increase “set remotetimeout” in GDB.

I create a .gdbinit at the root level of my project, with the statement: set remotetimeout 2 (for 2000ms), but without any effect.

2 - Same question for:
esp_cpu_compare_and_set (addr=0x3ffc08cc <s_phy_int_mux>, compare_value=1074341400, new_value=3007315967) at C:\Users\XXXX.platformio\packages\framework-espidf\components\esp_hw_support\cpu.c:628
628 {

3 - How do you explain the message:
Target is already running an algorithm

Thank you for your help.

Can you upload a complete minimal project that reproduces your error?

Thanks maxgerharst, the link gives you access to the program I am unable to start a debugging session with.
In the log folder, you will find the monitoring logs in release and debug mode. Thanks for your help.