Re: How to use a gdb-stub?

[TriKri]

In my case, I use a JTAG to communicate with the target system's CPU (a
MIPS), so I don't think gdb-server will do the thing. I will need to have
some software running on the local machine, or at least a machine connected
to the debugging host via ethernet (since I guess gdb itself can't talk over
a JTAG); the target system is not connected via ethernet, since a JTAG is in
between. I already have software to communicate with the target system
through the JTAG, I just can't figure out (reading the gdb manual) how to
integrate it with gdb, that's what I'm trying to find out.

I read in a forum that the OpenOCD (open on chip debug) program uses TCP/IP
port 3333 (by default) to communicate with gdb. It was stated that the
common case is to run gdb on the same machine and connect to the localhost.
I would probably have to do the same thing, since I use a JTAG (that's what
OpenOCD expects too).


peter choi wrote:
> 
> by gdb-stub, do you mean the gdb-server??? gdb-server should run on the
> target machine.
> gdb-server communicate with gdb thru' either serial port or ethernet.
> 
> 
> TriKri wrote:
>> 
>> I'm making a new try. I have understood that the gdb-stub is supposed to
>> be linked to my debug daemon, which shall handel communication with the
>> embedded system CPU. Is the daemon supposed to be running on the local
>> machine (the one with gdb running) or on the target? Another thing, how
>> do gdb and the daemon communicate? If they are running on the same
>> machine, do they communicate through files? If they are running on
>> different machines (gdb on the local machine and the daemon on the
>> target), how do they communicate then?
>> 
>> /Kristofer
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-use-a-gdb-stub--tp18964766p19009776.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.