public inbox for
help / color / mirror / Atom feed
Subject: ecos/packages/kernel/current ChangeLog doc/ker ...
Date: Thu, 12 Dec 2002 10:31:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	2002-12-12 10:31:51

Modified files:
	packages/kernel/current: ChangeLog 
	packages/kernel/current/doc: kernel.sgml 
	packages/kernel/current/host/instr: dump_instr.c 
	packages/kernel/current/include: instrmnt.h instrument_desc.h 
	packages/kernel/current/src/common: kapi.cxx thread.cxx 
	packages/kernel/current/src/instrmnt: meminst.cxx 

Log message:
	* src/common/kapi.cxx:
	* include/kapi.h:
	Added function cyg_thread_get_next(), cyg_thread_find() and
	cyg_thread_get_info() to allow the current set of threads to be
	enumerated, and per-thread information to be retrieved safely.
	* doc/kernel.sgml: Documented new KAPI calls.
	* src/common/thread.cxx: Zero unique_id in thread destructor so
	that a stale thread pointer can be checked for validity.
	* include/instrmnt.h:
	Added cyg_instrument_state() to report the current state of an
	instrumentation flag.
	Moved ifdef for CYGDBG_KERNEL_INSTRUMENT_MSGS out of within FLAGS
	ifdef. We can have messages without flags.
	* src/instrmnt/meminst.cxx:
	Added cyg_instrument_state() to report the current state of an
	instrumentation flag.
	Modified cyg_instrument_msg() in line with header and table
	* host/instr/dump_instr.c:
	* host/instr/
	* include/instrument_desc.h:
	Added a final NULL element to the generated table in
	instrument_desc.h to mark its end. Otherwise code that does not
	have access to the table definition cannot find its end. Also
	added ifdefs to allow instrument_desc.h to be used to acquire the
	structure definition and table pointer.

             reply	other threads:[~2002-12-12 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 10:31 nickg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-24 11:37 jld
2006-08-21 17:13 jlarmour
2006-04-11 19:18 asl
2005-11-23 20:58 asl
2004-04-14  9:32 asl
2004-03-04  2:17 jlarmour
2003-12-09 15:10 gthomas
2003-07-02  3:39 jlarmour
2003-01-22  6:39 jlarmour
2002-10-01 12:10 jlarmour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).