From: Daniel Jacobowitz <dan@codesourcery.com>
To: Steffen Dettmer <steffen.dettmer@googlemail.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver 7.1 unable to read registers
Date: Mon, 27 Sep 2010 14:44:00 -0000 [thread overview]
Message-ID: <20100927144444.GA29773@caradoc.them.org> (raw)
In-Reply-To: <AANLkTin_JX+2mFw26oUOn6KmVu2uxqY4J+6LTXhG7kxW@mail.gmail.com>
On Mon, Sep 27, 2010 at 12:25:38PM +0200, Steffen Dettmer wrote:
> I do not see an XML warning message when gdb tries to connect,
> but I have a problem with "call" in remote debugging
> (arm-elf-nonlinux-gdb-7.20):
>
> (gdb) p strlen("")
> Could not write register "cpsr"; remote failure reply 'E00'
> An error occurred while in a function called from GDB.
> Evaluation of the expression containing the function
> (malloc) will be abandoned.
> When the function is done executing, GDB will silently stop.
>
> Could this be caused by missing expat support, or would I
> definitely see a XML warning message in case?
No, this will not be related. GDB always warns if it needs XML but
doesn't have expat.
This looks like a problem with your remote stub, specifically, what it
says on the cover: failed to write to cpsr.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-09-27 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 17:17 William Wagner
2010-09-24 7:47 ` Jan Kratochvil
2010-09-24 7:54 ` William Wagner
2010-09-24 13:30 ` Jon Smirl
2010-09-24 12:58 ` Ulrich Weigand
2010-09-24 13:36 ` Pedro Alves
2010-09-24 13:44 ` William Wagner
2010-09-24 14:05 ` Ulrich Weigand
2010-09-24 14:39 ` Pedro Alves
2010-09-27 10:25 ` Steffen Dettmer
2010-09-27 14:44 ` Daniel Jacobowitz [this message]
2010-10-07 17:16 ` Ulrich Weigand
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=20100927144444.GA29773@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=steffen.dettmer@googlemail.com \
/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