Static memory footprint analysis

[Ingolf Steinbach]

Thanks, Chris.

2009/3/10 Chris Johns <chrisj at rtems.org>:
> The libc, networking or other services could be calling malloc. For example
> printf will cause stdout to allocate a buffer.

No networking/printf. However, I see that malloc() is pulled in
nevertheless, so probably, there's some RTEMS code requiring it.

> Newer versions of RTEMS have heap reporting functions that help here.

What should I look at in order to evaluate the actual (run-time)
memory footprint for 4.6.5?

Kind regards
Ingolf