Re: gdbserver error (getprotobyname)

[Daniel Jacobowitz <drow@mvista.com>]

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