gdb remote debugging problems

  gdb   serial   remote debugging   win7   sparc

sparc board to do the development , the PC is win7, with the host computer via two COM ports (COM1, COM4) is connected , grmon through COM4 download the program to the next bit machine , then let sparc-elf-gdb through COM1 mouth to debug procedures. Excuse me, this idea could achieve ?
------ Solution ---------------------------------------- ----
gdb remote debugging via serial port did not seem to have seen , used network port

------ Solution ------------------------------------ --------
can use serial debugging , but I have not tried it for myself .
------ Solution ---------------------------------------- ----
network port is possible, tried.
------ Solution ---------------------------------------- ----


general process ( provided that can be networked ) :
on the target board to start gdbserver: gdbserver localhost: 2001 < program name >
start a remote session on the development host : xxx-arm-xxx-gdb-q < program name >
(gdb) target remote < target IP>: 2001

concrete can google it.
------ Solution ---------------------------------------- ----
input gdb debugging command to initialize
basic command
target remote: ip_address
load
If you use this computer
target remote localhost: 2331
load
------ For reference only -------------------------------- -------


inform in detail about how to operate, thank you !
------ For reference only -------------------------------------- -

also give a detailed talk about how, thank you !
------ For reference only -------------------------------------- -
problem has been resolved, this idea can be realized , which should be in accordance with the format RSP protocol handshake response can, by logging files (set remotelogfile log name --- command to open the log function ) can first view the sparc board when debugging is how handshake response , and then simulate this handshake in serial debugging answer , so you can debug serial port through a non- DSU.
Note : Be sure to try several times , especially in the case of multi-core board . Because I was in a single experiment , the emergence of another nuclear shut down the serial port on the phenomenon does not answer !