Update debugging.rst

[vrmay23]

• Add right path for debug (nuttx /)
• Support for debug not only on ESP32 arch (target extended-remote) but also for STM32 chip arch (target remote :3333)

Note: Please adhere to Contributing Guidelines.

Summary

Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.

Impact

Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.

Testing

Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.

[simbit18]

tar -> target

[acassis]

@simbit18 I use "tar" here too, since GDB accept reduced from (tar: target; mon: monitor, etc). But maybe it is better to use the formal way

[simbit18]

Hi @acassis I also use the abbreviated form but I think for documentation the unabbreviated form is preferable.

[hartmannathan]

Hi, agreed the un-abbreviated form is preferred in documentation, but I have another question:

According to the openocd docs, they show target extended-remote and they say that "If any backward compatibility issue requires using the old remote protocol in place of the extended remote one, the former protocol is still available through" target remote.

According to the GDB manual, section 20.1 compares target remote to target extended-remote and it looks like target extended-remote is newer/preferred if it works.

So, is there a reason you're changing from target extended-remote to target remote and, if so, could the documentation say why? For example, "We are using target remote rather than target extended-remote because the latter interferes with blah blah blah"

Thanks!

[hartmannathan]

Or, alternately, something like this:

Inside gdb console, connect to the gdb server with:

(gdb) target extended-remote :3333

If this doesn't work as expected, try the older remote protocol with:

(gdb) target remote :3333