information about resources of actual application

[Jan.Suchotzki at de.abb.com]

Hi,

>With CPU_usage_dump() you can see this.
>With malloc_dump() you can see the memory usage.

The function CPU_usage_dump() works fine and helps a lot.

But I run in trouble with malloc_dump(). When I call this
function nothing happens. I saw that I went into a version of malloc_dump()
with an empty body (only return) while debugging my application.
I recognised, that the right version (which makes some output) of
malloc_dump()
will be called only if RTEMS_DEBUG is defined.
I have compiled and installed my Snapshot with VARIANT=DEBUG and compile my
appilcation with make debug. I´ve included rtems/libcsupport.h for
malloc_dump().

Can somebody tell me why it didn´t work? I try to execute it with the
m68k-efi332 bsp.

>In my shell.c I can exec interactively these functions and tasks and more
>to examinate the cpu load, task list, memory usage, number of resources
>used...

I´ve tried it out, but also here are some problems. I´ve found an example
application you posted to the list on 7.9.2001. It´s for a pc386 BSP but I
think
with some modification it should work on a m68k BSP too.
The first problem was the configure_memory_overhead 16386. I´ve deleted
this line
because my application crashed. When I run the example I see one line on
the console
with some hieroglyphic characters. But I didn´t see a prompt and I can´t do
some
inputs.

Do you have an idea what happens?

>All of this is ready for you now with the last snapshot.
>Fernando RUIZ CASAS
>home:correo at fernando-ruiz.com
>work:fernando.ruiz at ctv.es

regards

Jan Suchotzki