From: "Peter Skvarka" <ps@softinengines.com>
To: <gdb@sourceware.org>
Subject: RE: RMT ERROR : failed to get remote thread list
Date: Wed, 19 Sep 2007 14:23:00 -0000 [thread overview]
Message-ID: <20070919142115.044421973AD@debian.softinengines.com> (raw)
In-Reply-To: <20070919132008.GA29463@caradoc.them.org>
I need to run "info threads" dgb command to see address of text section for
some running executable.
Does not exist some other way how to determine address of text section of
loaded executable ?
"info threads" is in gdb only way I know, but I dont know gdb very good.
Thanks !
Peter
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Wednesday, September 19, 2007 3:20 PM
To: Peter Skvarka
Cc: gdb@sourceware.org
Subject: Re: RMT ERROR : failed to get remote thread list
On Wed, Sep 19, 2007 at 02:46:00PM +0200, Peter Skvarka wrote:
> I use arm-elf-insight version 6.6 and after success connect into
> OpenOCD with JTAG, I am trying to issue in gdb console:
> "info threads"
If you are using a JTAG device to talk to your target, it probably does not
support threads. However, it looks like it is not correctly reporting that
it does not support threads.
> after it there is displayed two dialog boxes:
> "RMT ERROR : failed to get remote thread list"
> and
> "couldn't restore frame in current thread, at frame 0"
>
> What does it mean this error ? How can I correct it ?
Compare the remote protocol manual with what OpenOCD is doing, and change
OpenOCD's behavior to correctly report unsupported commands.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-19 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 13:20 Peter Skvarka
2007-09-19 13:31 ` Daniel Jacobowitz
2007-09-19 14:23 ` Peter Skvarka [this message]
2007-09-19 14:58 ` Daniel Jacobowitz
2007-09-19 20:20 ` Peter Skvarka
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=20070919142115.044421973AD@debian.softinengines.com \
--to=ps@softinengines.com \
--cc=gdb@sourceware.org \
/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