public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Stanislav Meduna <stano@meduna.org>
Cc: openocd-devel@lists.sourceforge.net, ecos-devel@ecos.sourceware.org
Subject: Re: [OpenOCD-devel] Thread awareness with eCos problem
Date: Sat, 19 May 2012 14:49:00 -0000	[thread overview]
Message-ID: <20120519144905.GD1398@home.lan> (raw)
In-Reply-To: <4FB79716.9030101@meduna.org>

Hi,

On Sat, May 19, 2012 at 02:50:30PM +0200, Stanislav Meduna wrote:
> (it depends on what symbols the OpenOCD has an access to),

Basically, if you can load the elf file in gdb and you can "print" the
needed variable, then OpenOCD has access to it too (because it
basically asks gdb for the offset of a variable it needs).

HTH
-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  reply	other threads:[~2012-05-19 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 12:51 Stanislav Meduna
2012-05-19 14:49 ` Paul Fertser [this message]
2012-05-28 15:05   ` [OpenOCD-devel] " Stanislav Meduna
2012-05-28 15:55     ` Paul Fertser

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=20120519144905.GD1398@home.lan \
    --to=fercerpav@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=openocd-devel@lists.sourceforge.net \
    --cc=stano@meduna.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).