public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Good Guy <gooodguy@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: listing all threads
Date: Wed, 23 Nov 2005 10:13:00 -0000	[thread overview]
Message-ID: <m3mzjv7jvd.fsf@xl5.calivar.com> (raw)
In-Reply-To: <1132715082.2805.61.camel@hermes>

Gary Thomas <gary@mlbassoc.com> writes:

> On Tue, 2005-11-22 at 15:12 -0800, Good Guy wrote:
> > I was looking for a utility function which will list all the threads
> > (and state associated with each thread) in a running system. Does such
> > a function or some sample code to help write this function exist? I'm
> > using ecos 1.3.1.
>         ^^^^^^^^^^
> Now some 5+ years old, so you may have challenges ahead.  Why not
> update?
> 
> Any way, the basic code to do this is in the GDB stubs.  Look at
>   .../hal/common/<VERSION>/src

There's an API to do this from user code. Take a look at
cyg_thread_get_info() and friends. It is described in the
documentation. However, it is not present in 1.3.1.


-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-11-23 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a395a2600511221452l4171a814v8de90241417db6f4@mail.gmail.com>
2005-11-22 23:12 ` Good Guy
2005-11-23  3:05   ` Gary Thomas
2005-11-23 10:13     ` Nick Garnett [this message]
2005-11-23 20:29 Zimman, Chris

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=m3mzjv7jvd.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gooodguy@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).