Issues with remote debugging of gdbserver

[hamigua9527]

I would like to ask, when the firmware simulation runs successfully, how can I choose debug mode 4 to debug the additional process for gdbserver? However, because the IP address of the virtual network card TAP2 is 192.168.0.1, how can I remotely debug through the local area network?

[hanteed]

If you want to debug from another machine (your host for example if your firmware runs inside a VM) you can forward any distant connections to the debugging port. You can for example use socat.

Listen on port 1338 and redirect every requests on the emulated device at 192.168.0.1:1337 :
sudo socat TCP-LISTEN:1338, fork TCP:192.168.0.1:1337

Start your debugging session from a distant machine :
gdb-multiarch -ex "target remote 192.168.56.110:1338"