From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dcmail1.waves.com (dcmail1.waves.com [12.34.136.6]) by ozlabs.org (Postfix) with SMTP id 2FDC4DDE3E for ; Tue, 20 Feb 2007 03:48:10 +1100 (EST) From: "Ami Levi Waves" To: Subject: gdb - dgbserver problem Date: Mon, 19 Feb 2007 17:40:31 +0100 Message-ID: <000801c75444$c5e24c40$0600000a@waves.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C7544D.27A6B440" Reply-To: ami@waves.com List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C7544D.27A6B440 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Hi there, I'm having a problem when using gdb to debug an application via the gdbserver. It seems the gdbserver crashes when I issue "continue" = command (the target just hangs, no response, no messages on the Linux console). This is what I'm getting on the gdb side (I'm using verbose and debug modes): (gdb) continue Continuing. Sending packet: $Z0,100004dc,4#02...Ack Packet received: Packet Z0 (software-breakpoint) is NOT supported Sending packet: $m100004dc,4#b9...Ack Packet received: 3d201000 Sending packet: $X100004dc,0:#da...Ack Packet received: binary downloading NOT suppported by target Sending packet: $M100004dc,4:7d821008#a1...Ack Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $m3000c380,4#8e...Sending packet: = $m3000c380,4#8e...Sending packet: $m3000c380,4#8e...Sending packet: $m3000c380,4#8e...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Reply contains invalid hex digit 116 =20 Here are a few words about my setup: I'm using an Arabella 2.6.12 custom kernel that contains USB support. Everything is working fine (Except for this problem). I'm using the new DENX 4.1 toolchain to compile both my kernel & application. I'm using Fedora desktop to run the gdb and the gdbserver = is on my custom MPC880 board.=20 I'm using IP to connect the gdb to gdbserver. I'm following the exact guidelines described on DENX web site.=20 In order to simplify the problem I'm using a simple "hello world" = program.=20 Any ideas? Thanks. Ami Levi ------=_NextPart_000_0009_01C7544D.27A6B440 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Hi there,

I’m having a problem = when using gdb to debug an application via the gdbserver. It seems the gdbserver = crashes when I issue “continue” command (the target just hangs, no = response, no messages on the Linux console).

This is what I’m = getting on the gdb side (I’m using verbose and debug = modes):

(gdb) continue

Continuing.

Sending packet: $Z0,100004dc,4#02...Ack

Packet received:

Packet Z0 (software-breakpoint) is NOT = supported

Sending packet: $m100004dc,4#b9...Ack

Packet received: 3d201000

Sending packet: $X100004dc,0:#da...Ack

Packet received:

binary downloading NOT suppported by target

Sending packet: $M100004dc,4:7d821008#a1...Ack

Timed out.

Timed out.

Timed out.

Ignoring packet error, continuing...

Sending packet: $m3000c380,4#8e...Sending packet: = $m3000c380,4#8e...Sending packet: $m3000c380,4#8e...Sending packet: $m3000c380,4#8e...Timed = out.

Timed out.

Timed out.

Ignoring packet error, continuing...

Reply contains invalid hex digit 116

 

Here are a few words about = my setup:

I’m using an Arabella = 2.6.12 custom kernel that contains USB support. Everything is working fine = (Except for this problem).

I’m using the new = DENX 4.1 toolchain to compile both my kernel & application. I’m using Fedora = desktop to run the gdb and the gdbserver is on my custom MPC880 board. =

I’m using IP to = connect the gdb to gdbserver. I’m following the exact guidelines described on = DENX web site.

In order to simplify the = problem I’m using a simple “hello world” program.

Any = ideas?

Thanks.

Ami = Levi

------=_NextPart_000_0009_01C7544D.27A6B440--