[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Static memory footprint analysis
- Date: Tue, 10 Mar 2009 09:03:18 +0100
- From: ingolf.steinbach at googlemail.com (Ingolf Steinbach)
- Subject: Static memory footprint analysis
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?