From:	Richard Dawe <rich AT tudor21 DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: problem with new malloc.c attn: Eli Zaretskii
Date:	Mon, 27 Sep 1999 20:08:38 +0100
Organization:	Customer of Planet Online
Lines:	21
Message-ID:	<37EFC0B6.62903FC2@tudor21.net>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990927094243 DOT 8548D-100000 AT is>
NNTP-Posting-Host:	modem-28.tretinoin.dialup.pol.co.uk
Mime-Version:	1.0
X-Trace:	news8.svr.pol.co.uk 938554000 8677 62.136.90.28 (28 Sep 1999 21:26:41 GMT)
NNTP-Posting-Date:	28 Sep 1999 21:26:41 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.10 i586)
X-Accept-Language:	de,fr
X-NNTP-Posting-Host:	iolanthe.tudor21.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> > Remote-debugging via TCP/IP would be really cool, wouldn't it? ;-)
> 
> Actually, GDB already supports it.  Volunteers are welcome to make
> that support work with DJGPP.

Really? If I get time to look at it, I'll try to get gdb to compile with
network debugging support with libsocket. I'm not sure which will crash
first - the program or libsocket ;) - but it's worth a shot.

Does this requires some kind of stub code in the executable to communicate
across the network with the debugger? Or do you run the program in a
mini-gdb network server and then connect to it from a client gdb session?

Bye,

-- 
Richard Dawe
richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/

- Raw text -