From: David Jones <davidjones_home@yahoo.com>
To: gdb_list <gdb@sources.redhat.com>
Subject: gdbserver error (getprotobyname)
Date: Tue, 12 Feb 2002 22:40:00 -0000 [thread overview]
Message-ID: <20020213064037.92526.qmail@web13703.mail.yahoo.com> (raw)
Hi,
I am using gdbserver on a StrongArm board compiled
for arm-linux. On my Linux x86 host I am running
gdb compiled to debug an arm-linux target. Thanks
to Bill Gatliff for helping me out with this.
I can successfully debug a program if I use the serial
port between the host and the target. This is great!
However when I try to use a network connection I get
the following error: (below is a trace of my commands)
(target output)
----------------------------------------------------
# ./arm-linux-gdbserver davesplace:90 hello
Process hello created; pid = 180
getprotobyname: No such file or directory.
Exiting
(host output)
(gdb) target remote tuxscreen:90
Remote debugging using tuxscreen:90
Couldn't establish connection to remote target
Remote communication error: Connection reset by peer.
(gdb)
#
----------------------------------------------------
Has anyone seen this type of error (i.e. getprotobyname)?
I start the gdbserver first as recommended by the GDB documentation.
man getprotobyname shows:
The getprotobyname() function returns a protoent structure for the line from
/etc/protocols that matches the protocol name name.
The /etc/protocols file is present on my StrongArm target.
# more /etc/protocols
# /etc/protocols:
# $Id: protocols,v 1.1.1.1 2001/09/12 19:03:24 andersee Exp $
#
# Internet (IP) protocols
#
# from: @(#)protocols 5.1 (Berkeley) 4/17/89
#
# Updated for NetBSD based on RFC 1340, Assigned Numbers (July 1992).
ip 0 IP # internet protocol, pseudo protocol number
icmp 1 ICMP # internet control message protocol
igmp 2 IGMP # Internet Group Management
ggp 3 GGP # gateway-gateway protocol
ipencap 4 IP-ENCAP # IP encapsulated in IP (officially ``IP'')
st 5 ST # ST datagram mode
tcp 6 TCP # transmission control protocol
egp 8 EGP # exterior gateway protocol
pup 12 PUP # PARC universal packet protocol
udp 17 UDP # user datagram protocol
hmp 20 HMP # host monitoring protocol
xns-idp 22 XNS-IDP # Xerox NS IDP
rdp 27 RDP # "reliable datagram" protocol
iso-tp4 29 ISO-TP4 # ISO Transport Protocol class 4
xtp 36 XTP # Xpress Tranfer Protocol
ddp 37 DDP # Datagram Delivery Protocol
idpr-cmtp 39 IDPR-CMTP # IDPR Control Message Transport
rspf 73 RSPF #Radio Shortest Path First.
vmtp 81 VMTP # Versatile Message Transport
ospf 89 OSPFIGP # Open Shortest Path First IGP
ipip 94 IPIP # Yet Another IP encapsulation
encap 98 ENCAP # Yet Another IP encapsulation
#
By the way my StrongArm is a tuxscreen. (see www.tuxscreen.net)
David
__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com
next reply other threads:[~2002-02-13 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 22:40 David Jones [this message]
2002-02-12 23:10 ` Martin M. Hunt
2002-02-12 23:25 ` Daniel Jacobowitz
2002-02-13 7:13 ` Daniel Jacobowitz
2002-02-13 23:07 ` David Jones
2002-02-14 6:30 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020213064037.92526.qmail@web13703.mail.yahoo.com \
--to=davidjones_home@yahoo.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox