Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Jones <davidjones_home@yahoo.com>
To: gdb@sources.redhat.com
Subject: Re: gdbserver error (getprotobyname)
Date: Wed, 13 Feb 2002 23:07:00 -0000	[thread overview]
Message-ID: <20020214070702.5676.qmail@web13706.mail.yahoo.com> (raw)
In-Reply-To: <20020213101305.A32551@nevyn.them.org>


Hi All,
  Thanks for the comments and suggestions to my gdbserver problem.

> > The /etc/protocols file is present on my StrongArm target.  
> 
> Are /etc/nsswitch.conf and /lib/libnss_files* and friends?
> 
> But in any case I recommend Martin's patch.
> 

Daniel,
  I don't have /etc/nsswitch.conf and /lib/libnss_files* and friends
since I used a statically linked binary for the StrongArm given to me
by Bill.  I will check out the gdb source, apply Martin's patch, and
try to build gdb and gdbserver from the source.  One question though,
are there any special or unique options that I need to pass to the configure
script ? 

David

--- Daniel Jacobowitz <drow@mvista.com> wrote:
> On Tue, Feb 12, 2002 at 10:40:37PM -0800, David Jones wrote:
> > 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.  
> 
> Are /etc/nsswitch.conf and /lib/libnss_files* and friends?
> 
> But in any case I recommend Martin's patch.
> 
> -- 
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer


__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com


  reply	other threads:[~2002-02-14  7:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 22:40 David Jones
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 [this message]
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=20020214070702.5676.qmail@web13706.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