Mail Archives: djgpp/1999/09/30/13:00:07

From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: problem with new malloc.c attn: Eli Zaretskii
Date: Thu, 30 Sep 1999 13:30:12 +0200
Organization: NetVision Israel
Lines: 24
Message-ID: <Pine.SUN.3.91.990930133003.20873B-100000@is>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990927094243 DOT 8548D-100000 AT is> <37EFC0B6 DOT 62903FC2 AT tudor21 DOT net> <37F13B51 DOT E384B38E AT tudor21 DOT net>
Mime-Version: 1.0
X-Trace: 938690939 21097 (30 Sep 1999 11:28:59 GMT)
X-Complaints-To: abuse AT netvision DOT net DOT il
NNTP-Posting-Date: 30 Sep 1999 11:28:59 GMT
X-Sender: eliz AT is
In-Reply-To: <>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Tue, 28 Sep 1999, Richard Dawe wrote:

> Well, I just took a look and it appears its not quite that simple ;)
> TCP/IP is supported, but (only?) for VxWorks programs.

I'm not sure you looked in the right place.  Look in the gdb/gdbserver
directory (it might be missing from the DJGPP source distribution).

> I think maybe this would be slightly too ambitious. It may be better to
> use some kind of serial-to-TCP/IP conversion. I imagine the serial support
> is more robust than libsocket.

As far as I see, gdbserver supports both serial and TCP/IP, although
it's possible that the latter is not finished.  Even if so, it
shouldn't be hard to finish it, since the underlying protocol hardly
matters too much.  At least as far as DJGPP support is concerned, the
physical protocol is NOT the aspect that presents the major challenge.

> BTW I looked at the gdb 4.16 sources, so maybe things have advanced since
> then?

A lot has changed.  Please look in the latest version on GNU FTP

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019