From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-17661-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 17056 invoked by alias); 18 Mar 2004 22:14:19 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 17047 invoked from network); 18 Mar 2004 22:14:16 -0000
Received: from unknown (HELO mms1.broadcom.com) (63.70.210.58)
  by sources.redhat.com with SMTP; 18 Mar 2004 22:14:16 -0000
Received: from 63.70.210.1 by mms1.broadcom.com with ESMTP (Broadcom
 SMTP Relay (MMS v5.6.0)); Thu, 18 Mar 2004 14:14:12 -0800
X-Server-Uuid: 97B92932-364A-4474-92D6-5CFE9C59AD14
Received: from nt-sjca-0740.brcm.ad.broadcom.com (
 nt-sjca-0740.sj.broadcom.com [10.16.192.49]) by
 mon-irva-11.broadcom.com (8.9.1/8.9.1) with ESMTP id OAA10036 for
 <gdb@sources.redhat.com>; Thu, 18 Mar 2004 14:13:23 -0800 (PST)
Received: from nt-sjca-0741.brcm.ad.broadcom.com ([10.16.192.42]) by
 nt-sjca-0740.brcm.ad.broadcom.com with Microsoft SMTPSVC(5.0.2195.6713)
 ; Thu, 18 Mar 2004 14:13:55 -0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: remote debug broken?
Date: Thu, 18 Mar 2004 22:14:00 -0000
Message-ID: <02B1C56408AC9140BAE3395894D2DB3C0BA8B2@nt-sjca-0741.sj.broadcom.com>
From: "Robert Trask" <rtrask@broadcom.com>
To: gdb@sources.redhat.com
X-OriginalArrivalTime: 18 Mar 2004 22:13:55.0791 (UTC)
 FILETIME=[4DCD45F0:01C40D36]
X-WSS-ID: 6C44C0BE1NO7352263-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2004-03/txt/msg00177.txt.bz2

Hello,
I want to use the remote debug feature on gdb wherein I have a
[superior] debugger running on a host system (Linux I386 pc) and an
[inferior] debugger running on the target (embedded Linux on MIPS). I
have tried this in gdb v5.3 and v6.0, the same behavior results.

I built the superior debugger in the usual way:
./configure        // build for native operation
make
then installed in my bin directory.

I built the inferior debugger in the gdbserver directory:
mkdir mipsobj
cd mipsobj
setenv CC <my mips cross gcc path>
../configure mips-linux-gnu
make

And then installed on my target...


I then start up the inferior debugger (gdbserver) on the target:

gdbserver host:tcp_port <prog-to-debug>

This obligingly waits for the superior debugger to contact it and start
matters.

I start gdb on the host in the usual way:

gdb <prog-to-debug>

then:
(gdb) target remote 10.18.99.108:6001
Remote debugging using 10.18.99.108:6001
Sending packet: $Hc-1#09...Ack
Packet received: OK
Sending packet: $qC#b4...Ack
Packet received:=20
Sending packet: $qOffsets#4b...Ack
Packet received:=20
Sending packet: $?#3f...Ack
Packet received: T0525:2aac0e50;1d:7fff7ee0;
Couldn't establish connection to remote target
Reply contains invalid hex digit 59


The hex digit 59 is a semicolon. Looking at the gdbserver sources I can
see it thinks (correctly) it's replying to a resume command and
expressly uses semicolons as field delimiters.

Am I missing an important step somewhere, doing something dumb,  or
both? Does remote debugging no longer work? Any ideas or suggestions
would be appreciated.

thanks!

/bob