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]

profiler & memory leak detector


Try as I may, I cannot post this to the ecos-devel list, although I am
signed up for it, so I'm going to post it here in the discussion list.

Has or does anybody use vxWorks?

If you have, you may have used their profiler.  I have a very simple
profiler that I can make available for the x86 PC target.  I would like to
know if there would be any interest in making such a beast available in the
main tree?  It requires a modification in the kernel in vectors.S.
Basically, I just detect interrupts with vector 0x20 (the 10 msec interrupt)
and record the last function the program was in when the periodic system
tick fired.  I know this has some problems, namely anything that has a delay
is tied to the system tick, but for stressed systems it gives a pretty
accurate view of what functions you have to streamline.

VxWorks also has a tool called memtool.  It just detects which functions
(and if memory serves tasks) allocate and dealloc memory and in which heap.
This is useful for detecting memory leaks although not extremely useful.  I
don't have a similar tool, but I can make one.

Is there any interest in putting these into the main tree?  Putting in HOOKS
to do it is very easy, and I would like to do that if there is any interest
in incorporating it into the main tree.

The profiler is very architecture dependant so I need help making that work
for other platforms than x86 PC.

-Rich


-- 
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]