delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/08/17/05:16:44

Xref: news2.mv.net comp.os.msdos.djgpp:7428
From: alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Remote debuggery with GDB
Date: Tue, 06 Aug 1996 17:14:02 GMT
Lines: 36
Message-ID: <839351526.10205.0@abwillms.demon.co.uk>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960805195204 DOT 13089C-100000 AT is>
NNTP-Posting-Host: abwillms.demon.co.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:


>On Mon, 5 Aug 1996, Cesar Scarpini Rabak wrote:

>> In the info file about gdb there is a full chapter in remote debugging. In a
>> nutshell, you have to set a kind of server in the debuggee program which
>> will work trhough a protocol described in the document. 
>> 
>> The hard part is that IFAIK there is not one such implementation (yet) for
>> DJGPP.

>There *is* a DJGPP-specific support for remote debugging in GDB, but it 
>was done for DJGPP v1.x, and nobody ported it to v2.0.  So it doesn't 
>work.

Yeah, but that's not what I mean (not the server thing). I just want
to route gdb CONSOLE I/O to the other computer so mine can hit GFX
mode - better than routing gdb to the printer as described in the FAQ,
no?

What I meant was, will it survive being totally rerouted to the com
port, or does it get keyboard input from IRQ9, which I presume it
hooks for Ctrl+Break - which I would have to push on the execution
machine, not the remote terminal!

Regards,


ABW
--
I have become... Comfortably numb...

Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk
<A HREF="http://www.hardcafe.co.uk/Alaric/">http://www.hardcafe.co.uk/Alaric/</A>

- Raw text -


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