Hi,

As long as you don't use the following mpatrol options, then your
program's heap will be reasonably compact, as you'd expect:

NOFREE, OFLOWSIZE, PAGEALLOC

However, the library will still use quite a lot of memory for its
internal record-keeping, such as symbolic stack traces, profiling,
tracing, etc. You don't really have any control over whether mpatrol
reads symbols or not, but you could always recompile the library to
disable that, probably saving quite a lot of memory but losing that
capability. The following options will increase the amount of memory
mpatrol uses internally:

PROF, TRACE, USEDEBUG

You mention that the program should "log on further and not stop when
not being loaded completely". Is it stopping because you're running
out of memory? How much memory do you have available on your embedded
system? What is the OS that it's running on? Is it an embedded Linux
such as ucLinux?

Remember that you don't need to log everything from mpatrol. If there
is an error, mpatrol will log it automatically. If the log file is
being placed in a ram disk on your system then cutting the size of the
log file might give you more memory to run your program.

Graeme.

--- In mpatrol@yahoogroups.com, "fsoenmez" <fsoenmez@...> wrote:
>
> Hi,
>
> on our PowerPC we start our software with mpatrol, which creates a
> very big logfile (105 MB). The memory allocation grows to big (twice
> as big as usually). The program should log on further and not stop
> when not being loaded completely.
>
> Does anybody have an idea how it can be avoided that the program stops
> and needs such a big memory allocation?
> What do you suggest to get an acceptable result?
>
> Kind regards & thank you
>
> Fahri
>