OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-old/] [gdb-7.1/] [gdb/] [gdbserver/] [README] - Blame information for rev 842

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 227 jeremybenn
                   README for GDBserver & GDBreplay
2
                    by Stu Grossman and Fred Fish
3
 
4
Introduction:
5
 
6
This is GDBserver, a remote server for Un*x-like systems.  It can be used to
7
control the execution of a program on a target system from a GDB on a different
8
host.  GDB and GDBserver communicate using the standard remote serial protocol
9
implemented in remote.c, and various *-stub.c files.  They communicate via
10
either a serial line or a TCP connection.
11
 
12
For more information about GDBserver, see the GDB manual.
13
 
14
Usage (server (target) side):
15
 
16
First, you need to have a copy of the program you want to debug put onto
17
the target system.  The program can be stripped to save space if needed, as
18
GDBserver doesn't care about symbols.  All symbol handling is taken care of by
19
the GDB running on the host system.
20
 
21
To use the server, you log on to the target system, and run the `gdbserver'
22
program.  You must tell it (a) how to communicate with GDB, (b) the name of
23
your program, and (c) its arguments.  The general syntax is:
24
 
25
        target> gdbserver COMM PROGRAM [ARGS ...]
26
 
27
For example, using a serial port, you might say:
28
 
29
        target> gdbserver /dev/com1 emacs foo.txt
30
 
31
This tells gdbserver to debug emacs with an argument of foo.txt, and to
32
communicate with GDB via /dev/com1.  Gdbserver now waits patiently for the
33
host GDB to communicate with it.
34
 
35
To use a TCP connection, you could say:
36
 
37
        target> gdbserver host:2345 emacs foo.txt
38
 
39
This says pretty much the same thing as the last example, except that we are
40
going to communicate with the host GDB via TCP.  The `host:2345' argument means
41
that we are expecting to see a TCP connection from `host' to local TCP port
42
2345.  (Currently, the `host' part is ignored.)  You can choose any number you
43
want for the port number as long as it does not conflict with any existing TCP
44
ports on the target system.  This same port number must be used in the host
45
GDBs `target remote' command, which will be described shortly.  Note that if
46
you chose a port number that conflicts with another service, gdbserver will
47
print an error message and exit.
48
 
49
On some targets, gdbserver can also attach to running programs.  This is
50
accomplished via the --attach argument.  The syntax is:
51
 
52
        target> gdbserver --attach COMM PID
53
 
54
PID is the process ID of a currently running process.  It isn't necessary
55
to point gdbserver at a binary for the running process.
56
 
57
Usage (host side):
58
 
59
You need an unstripped copy of the target program on your host system, since
60
GDB needs to examine it's symbol tables and such.  Start up GDB as you normally
61
would, with the target program as the first argument.  (You may need to use the
62
--baud option if the serial line is running at anything except 9600 baud.)
63
Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'.  After that, the only
64
new command you need to know about is `target remote'.  It's argument is either
65
a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT
66
descriptor.  For example:
67
 
68
        (gdb) target remote /dev/ttyb
69
 
70
communicates with the server via serial line /dev/ttyb, and:
71
 
72
        (gdb) target remote the-target:2345
73
 
74
communicates via a TCP connection to port 2345 on host `the-target', where
75
you previously started up gdbserver with the same port number.  Note that for
76
TCP connections, you must start up gdbserver prior to using the `target remote'
77
command, otherwise you may get an error that looks something like
78
`Connection refused'.
79
 
80
Building gdbserver:
81
 
82
The supported targets as of November 2006 are:
83
        arm-*-linux*
84
        crisv32-*-linux*
85
        cris-*-linux*
86
        i[34567]86-*-cygwin*
87
        i[34567]86-*-linux*
88
        i[34567]86-*-mingw*
89
        ia64-*-linux*
90
        m32r*-*-linux*
91
        m68*-*-linux*
92
        m68*-*-uclinux*
93
        mips*64*-*-linux*
94
        mips*-*-linux*
95
        powerpc[64]-*-linux*
96
        s390[x]-*-linux*
97
        sh-*-linux*
98
        spu*-*-*
99
        x86_64-*-linux*
100
        xscale*-*-linux*
101
 
102
Configuring gdbserver you should specify the same machine for host and
103
target (which are the machine that gdbserver is going to run on.  This
104
is not the same as the machine that gdb is going to run on; building
105
gdbserver automatically as part of building a whole tree of tools does
106
not currently work if cross-compilation is involved (we don't get the
107
right CC in the Makefile, to start with)).
108
 
109
Building gdbserver for your target is very straightforward.  If you build
110
GDB natively on a target which gdbserver supports, it will be built
111
automatically when you build GDB.  You can also build just gdbserver:
112
 
113
        % mkdir obj
114
        % cd obj
115
        % path-to-gdbserver-sources/configure
116
        % make
117
 
118
If you prefer to cross-compile to your target, then you can also build
119
gdbserver that way.  In a Bourne shell, for example:
120
 
121
        % export CC=your-cross-compiler
122
        % path-to-gdbserver-sources/configure your-target-name
123
        % make
124
 
125
Using GDBreplay:
126
 
127
A special hacked down version of gdbserver can be used to replay remote
128
debug log files created by gdb.  Before using the gdb "target" command to
129
initiate a remote debug session, use "set remotelogfile " to tell
130
gdb that you want to make a recording of the serial or tcp session.  Note
131
that when replaying the session, gdb communicates with gdbreplay via tcp,
132
regardless of whether the original session was via a serial link or tcp.
133
 
134
Once you are done with the remote debug session, start gdbreplay and
135
tell it the name of the log file and the host and port number that gdb
136
should connect to (typically the same as the host running gdb):
137
 
138
        $ gdbreplay logfile host:port
139
 
140
Then start gdb (preferably in a different screen or window) and use the
141
"target" command to connect to gdbreplay:
142
 
143
        (gdb) target remote host:port
144
 
145
Repeat the same sequence of user commands to gdb that you gave in the
146
original debug session.  Gdb should not be able to tell that it is talking
147
to gdbreplay rather than a real target, all other things being equal.  Note
148
that gdbreplay echos the command lines to stderr, as well as the contents of
149
the packets it sends and receives.  The last command echoed by gdbreplay is
150
the next command that needs to be typed to gdb to continue the session in
151
sync with the original session.

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.