From: Eli Zaretskii 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: References: <37EFC0B6 DOT 62903FC2 AT tudor21 DOT net> <37F13B51 DOT E384B38E AT tudor21 DOT net> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 938690939 21097 199.203.121.2 (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: <37F13B51.E384B38E@tudor21.net> 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 Precedence: bulk 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 sites.