From: Daniel Jacobowitz <drow@false.org>
To: Efim Monjak <ymonyak@lipowsky.de>
Cc: gdb@sources.redhat.com
Subject: Re: remote failure reply
Date: Thu, 03 Nov 2005 21:19:00 -0000 [thread overview]
Message-ID: <20051103211915.GC11262@nevyn.them.org> (raw)
In-Reply-To: <436A5BA0.7090803@lipowsky.de>
On Thu, Nov 03, 2005 at 07:49:04PM +0100, Efim Monjak wrote:
> Hi all,
>
> I try to debug a relatively big programm with arm-elf-gdb 6.3.50. After
> a couple of steps I receive a failure message from GDB
> about register message. But later the GDB has receive an other register
> message withother failure.
> Can you tell me what is hier a problem? As I used GDB 6.1 I have had a
> problem with remote target
> depend on Walues in Registers. In this case GDB sent +---+--- .... In
> snapshort 6.3.50 it is fixed.
> Possibly it is now a similar problem.
This is why it's traditional to use lowercase hex, not uppercase, in
remote replies.
> Packet received:
> E03D004032000000D13C004002000000800000003CFEFF7F2C01004000000000DC813F28F26AC140F03B0040EC3D0040703C0040C83C0040F00F0080F40B0080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005F000020
This is interpreted as an error because it begins with 'E'.
Perhaps it shouldn't be, but for compatibility, I recommend fixing the
stub.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-03 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 18:49 Efim Monjak
2005-11-03 21:19 ` Daniel Jacobowitz [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=20051103211915.GC11262@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ymonyak@lipowsky.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).