From:	embeddedc AT hotmail DOT com (embeddedc)
Newsgroups:	comp.os.msdos.djgpp
Subject:	remote debug stub and Windows 2000
Date:	5 Feb 2003 11:28:46 -0800
Organization:	http://groups.google.com/
Lines:	34
Message-ID:	<eebb6570.0302051128.4ca566c@posting.google.com>
NNTP-Posting-Host:	80.74.171.13
X-Trace:	posting.google.com 1044473326 960 127.0.0.1 (5 Feb 2003 19:28:46 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	5 Feb 2003 19:28:46 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I have built a demo program that uses i386-stub.c to remote debug from
a Windows 2000 machine.  My target machine appears to work correctly. 
However I am having problems with GDB on the host.  I am using V5.3.

The problem is as follows:
 
+ I start the target – which contains a breakpoint() instruction.

+ I start GDB on the host, then type "target remote COM1".  I know the
host the transmits data correctly as I can see it arriving on the
target.

+ The first few commands transmitted by GDB are not supported by the
stub,
so I return $#00, as per the DGB FAQ.  I know the target transmits
this okay as I can see them arriving if I use a dumb terminal instead
of GDB.

+ GDB reports errors like "Ignoring packet error, continuing..." * 3,
then
"Couldn't establish connection to remote target ... Malformed response
to
offset query, timeout".

These errors make it look like GDB does not understand the reply -
however, if I unplug the serial cable the error messages are the same
so I think it is just that GDB is not seeing the replies at all.  On
the target Tx and Rx appear to work.  On the Windows 2000 host only Tx
appears to work.

Has anybody any experience of this?  Also, does GDB assume hardware
flow control over the serial port?

Thanks.

- Raw text -