IEP-1135 Incorrect default gdb executable for RISCV targets

[sigmaaa]

Description

Fixed debugger patterns to get correct gdb executables. The problem was, that without "$" at the end we could get the wrong executable, for example, bin\xtensa-esp32-elf-gdb-3.7.exe, etc.

Fixes # (IEP-1135)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How has this been tested?

Test 1:
try to debug with different targets
Test 2:
check the actual executable path in the debugger tab for different targets
Test Configuration:

• ESP-IDF Version:
• OS (Windows,Linux and macOS):

Dependent components impacted by this PR:

• Debugger tab

Checklist

• PR Self Reviewed
• Applied Code formatting
• Added Documentation
• Added Unit Test
• Verified on all platforms - Windows,Linux and macOS

[sigmaaa]

self reviewed

[kolipakakondal]

Hi @AndriiFilippov Can you please verify this

[AndriiFilippov]

@sigmaaa , @kolipakakondal hi !

Tested under:
OS: Windows 10 / MacOS
ESP-IDF: v5.1.2

LGTM 👍 Able to Debug.

1. on Windows: Debug works but for targets H2 / C6 the USB-JTAG ports are not identified in Launch Target :
   

2. all platforms: H2 target Debug starts very slow and with some errors like this:
   
   

3. in general, the Debug console is accompanied with errors like this, but without impact on Debug work.

Should I create separate tasks for those issues ?

[sigmaaa]

Hi @AndriiFilippov, yes we can create a separate issue for this since it's not related to the PR. Thanks