This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: C++ API Reference manual


On Mon, Aug 12, 2002 at 03:53:56PM +0100, Nick Garnett wrote:
> NavEcos <ecos@navosha.com> writes:
> 
> > The reason I started reading it is because I noticed that there
> > is additional functionality in the C++ interface not available in
> > the C interface, for example getting a thread's name or walking
> > through all the threads to check for stack usage, and other
> > nifty things.
> 
> These things are mostly there to aid GDB and other debugging
> features. I cannot immediately think of any use an application would
> have for them.

Our application uses this sort of information. When we panic for some
reason, we print out a list of threads and there current state. This
gives us an idea what was running, what threads could be in a deadlock
etc. This has proved useful when debugging, especially for devices in
the field where attaching gdb is not an option. To do this i used
dbg_getthreadreg() & dbg_threadinfo().

      Andrew


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]