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:29:57 +0200
Organization: NetVision Israel	
Lines: 12
Message-ID: <Pine.SUN.3.91.990930132930.20873A-100000@is>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990927094243 DOT 8548D-100000 AT is> <37EFC0B6 DOT 62903FC2 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 938690924 21092 199.203.121.2 (30 Sep 1999 11:28:44 GMT)
X-Complaints-To: abuse AT netvision DOT net DOT il
NNTP-Posting-Date: 30 Sep 1999 11:28:44 GMT
X-Sender: eliz AT is
In-Reply-To: <37EFC0B6.62903FC2@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 Mon, 27 Sep 1999, Richard Dawe wrote:

> 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?

The latter.  GDB includes a gdbserver program which runs on the target
(where the debugged program runs).  It controls the debugged program
and communicates with GDB that runs on the host.  In effect, it serves
as GDB's proxy on the target by executing GDB's commands and passing
the results back.