From: "Ami Levi Waves" <ami@waves•com>
To: "'Leonid'" <Leonid@a-k-a•net>, <linuxppc-embedded@ozlabs•org>
Subject: RE: gdb - dgbserver problem
Date: Tue, 20 Feb 2007 08:20:06 +0100 [thread overview]
Message-ID: <001401c754bf$a58a4ee0$0600000a@waves.com> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3CF9DD6E@ehost011-3.exch011.intermedia.net>
Hi Leonid,
You're the second person that tells me there might be a problem with
gdb-gdbserver in Fedora core (I'm using Fedora core 4).
I don't mind giving it a shot. I'll try to upgrade today to Fedora core =
5.
Thanks.
Ami
> -----Original Message-----
> From: Leonid [mailto:Leonid@a-k-a•net]
> Sent: Monday, February 19, 2007 5:54 PM
> To: ami@waves•com; linuxppc-embedded@ozlabs•org
> Subject: RE: gdb - dgbserver problem
>=20
> Which version of Fedora Core are u using? Because I experience similar
> problem (with different board though) and I have Fedora Core 4 while I
> know lady with precisely same setup and Fedora Core 5 and everything =
is
> working fine for her... so how stupid it may seem I started suspect =
FC4...
>=20
> Leonid.
>=20
> ________________________________________
> From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs•org
> [mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs•org] On =
Behalf
> Of Ami Levi Waves
> Sent: Monday, February 19, 2007 8:41 AM
> To: linuxppc-embedded@ozlabs•org
> Subject: gdb - dgbserver problem
>=20
>=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.
> 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
prev parent reply other threads:[~2007-02-20 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 16:40 gdb - dgbserver problem Ami Levi Waves
2007-02-19 16:54 ` Leonid
2007-02-20 7:20 ` Ami Levi Waves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001401c754bf$a58a4ee0$0600000a@waves.com' \
--to=ami@waves$(echo .)com \
--cc=Leonid@a-k-a$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox