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

Subversion Repositories or1k

[/] [or1k/] [trunk/] [gdb-5.0/] [gdb/] [gdbserver/] [gdbserver.1] - Diff between revs 107 and 1765

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 107 Rev 1765
.\" Copyright (c) 1993 Free Software Foundation
.\" Copyright (c) 1993 Free Software Foundation
.\" See section COPYING for conditions for redistribution
.\" See section COPYING for conditions for redistribution
.TH gdbserver 1 "2 November 1993" "Cygnus Support" "GNU Development Tools"
.TH gdbserver 1 "2 November 1993" "Cygnus Support" "GNU Development Tools"
.SH NAME
.SH NAME
gdbserver \- Remote Server for the GNU Debugger
gdbserver \- Remote Server for the GNU Debugger
.SH SYNOPSIS
.SH SYNOPSIS
.na
.na
.TP
.TP
.B gdbserver
.B gdbserver
.RB tty
.RB tty
.RB prog
.RB prog
.RB "[\|" args... "\|]"
.RB "[\|" args... "\|]"
.ad b
.ad b
.SH DESCRIPTION
.SH DESCRIPTION
GDBSERVER is a program that allows you to run GDB on a different machine
GDBSERVER is a program that allows you to run GDB on a different machine
than the one which is running the program being debugged.
than the one which is running the program being debugged.
Usage (server (target) side):
Usage (server (target) side):
First, you need to have a copy of the program you want to debug put onto
First, you need to have a copy of the program you want to debug put onto
the target system.  The program can be stripped to save space if needed, as
the target system.  The program can be stripped to save space if needed, as
GDBserver doesn't care about symbols.  All symbol handling is taken care of by
GDBserver doesn't care about symbols.  All symbol handling is taken care of by
the GDB running on the host system.
the GDB running on the host system.
To use the server, you log on to the target system, and run the `gdbserver'
To use the server, you log on to the target system, and run the `gdbserver'
program.  You must tell it (a) how to communicate with GDB, (b) the name of
program.  You must tell it (a) how to communicate with GDB, (b) the name of
your program, and (c) its arguments.  The general syntax is:
your program, and (c) its arguments.  The general syntax is:
        target> gdbserver COMM PROGRAM [ARGS ...]
        target> gdbserver COMM PROGRAM [ARGS ...]
For example, using a serial port, you might say:
For example, using a serial port, you might say:
        target> gdbserver /dev/com1 emacs foo.txt
        target> gdbserver /dev/com1 emacs foo.txt
This tells gdbserver to debug emacs with an argument of foo.txt, and to
This tells gdbserver to debug emacs with an argument of foo.txt, and to
communicate with GDB via /dev/com1.  Gdbserver now waits patiently for the
communicate with GDB via /dev/com1.  Gdbserver now waits patiently for the
host GDB to communicate with it.
host GDB to communicate with it.
To use a TCP connection, you could say:
To use a TCP connection, you could say:
        target> gdbserver host:2345 emacs foo.txt
        target> gdbserver host:2345 emacs foo.txt
This says pretty much the same thing as the last example, except that we are
This says pretty much the same thing as the last example, except that we are
going to communicate with the host GDB via TCP.  The `host:2345' argument means
going to communicate with the host GDB via TCP.  The `host:2345' argument means
that we are expecting to see a TCP connection from `host' to local TCP port
that we are expecting to see a TCP connection from `host' to local TCP port
2345.  (Currently, the `host' part is ignored.)  You can choose any number you
2345.  (Currently, the `host' part is ignored.)  You can choose any number you
want for the port number as long as it does not conflict with any existing TCP
want for the port number as long as it does not conflict with any existing TCP
ports on the target system.  This same port number must be used in the host
ports on the target system.  This same port number must be used in the host
GDBs `target remote' command, which will be described shortly.  Note that if
GDBs `target remote' command, which will be described shortly.  Note that if
you chose a port number that conflicts with another service, gdbserver will
you chose a port number that conflicts with another service, gdbserver will
print an error message and exit.
print an error message and exit.
Usage (host side):
Usage (host side):
You need an unstripped copy of the target program on your host system, since
You need an unstripped copy of the target program on your host system, since
GDB needs to examine it's symbol tables and such.  Start up GDB as you normally
GDB needs to examine it's symbol tables and such.  Start up GDB as you normally
would, with the target program as the first argument.  (You may need to use the
would, with the target program as the first argument.  (You may need to use the
--baud option if the serial line is running at anything except 9600 baud.)
--baud option if the serial line is running at anything except 9600 baud.)
Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'.  After that, the only
Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'.  After that, the only
new command you need to know about is `target remote'.  It's argument is either
new command you need to know about is `target remote'.  It's argument is either
a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT
a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT
descriptor.  For example:
descriptor.  For example:
        (gdb) target remote /dev/ttyb
        (gdb) target remote /dev/ttyb
communicates with the server via serial line /dev/ttyb, and:
communicates with the server via serial line /dev/ttyb, and:
        (gdb) target remote the-target:2345
        (gdb) target remote the-target:2345
communicates via a TCP connection to port 2345 on host `the-target', where
communicates via a TCP connection to port 2345 on host `the-target', where
you previously started up gdbserver with the same port number.  Note that for
you previously started up gdbserver with the same port number.  Note that for
TCP connections, you must start up gdbserver prior to using the `target remote'
TCP connections, you must start up gdbserver prior to using the `target remote'
command, otherwise you may get an error that looks something like
command, otherwise you may get an error that looks something like
`Connection refused'.
`Connection refused'.
.SH OPTIONS
.SH OPTIONS
You have to supply the name of the program to debug
You have to supply the name of the program to debug
and the tty to communicate on; the remote GDB will do everything else.
and the tty to communicate on; the remote GDB will do everything else.
Any remaining arguments will be passed to the program verbatim.
Any remaining arguments will be passed to the program verbatim.
.SH "SEE ALSO"
.SH "SEE ALSO"
.RB "`\|" gdb "\|'"
.RB "`\|" gdb "\|'"
entry in
entry in
.B info\c
.B info\c
\&;
\&;
.I
.I
Using GDB: A Guide to the GNU Source-Level Debugger\c
Using GDB: A Guide to the GNU Source-Level Debugger\c
, Richard M. Stallman and Roland H. Pesch, July 1991.
, Richard M. Stallman and Roland H. Pesch, July 1991.
.SH COPYING
.SH COPYING
Copyright (c) 1993 Free Software Foundation, Inc.
Copyright (c) 1993 Free Software Foundation, Inc.
.PP
.PP
Permission is granted to make and distribute verbatim copies of
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
this manual provided the copyright notice and this permission notice
are preserved on all copies.
are preserved on all copies.
.PP
.PP
Permission is granted to copy and distribute modified versions of this
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
permission notice identical to this one.
.PP
.PP
Permission is granted to copy and distribute translations of this
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
manual into another language, under the above conditions for modified
versions, except that this permission notice may be included in
versions, except that this permission notice may be included in
translations approved by the Free Software Foundation instead of in
translations approved by the Free Software Foundation instead of in
the original English.
the original English.
 
 

powered by: WebSVN 2.1.0

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