This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: support for remote/serial tcp not there linux host (maybe others too)
- To: niraj gupta <niraj at zumanetworks dot com>
- Subject: Re: support for remote/serial tcp not there linux host (maybe others too)
- From: Fernando Nasser <fnasser at cygnus dot com>
- Date: Wed, 02 Aug 2000 14:17:50 -0400
- CC: gdb at sources dot redhat dot com
- Organization: Red Hat , Inc. - Toronto
- References: <000001bffc38$2d418520$d301a8c0@internal.nbase.com>
Yes, he is right.
Something is wrong. When I try to connect to a TCP remote target I get:
totem:1234: Success.
What "Success" means in this case is that gdb could not find anyone to handle
tcp connections (should be "Unsuccess" :-) ).
Two errors in one. :-)
Fernando
P.S.: The "Success" message is easily avoided testing for NULL before calling
perror_with_name().
niraj gupta wrote:
>
> looks like this happened in gdb/Makefile.in version 1.39
> maybe following is the change which caused it
>
> in 1.38 it was
> SER_HARDWIRE = @SER_HARDWIRE@
>
> in 1.39 it is
> SER_HARDWIRE = ser-unix.o ser-pipe.o
>
> i would like to see ser-tcp.o back in Makefile.in
>
> THX
> niraj
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@cygnus.com