Re: OS X malloc problems

[Martin Pala]

Which monit version do you use?

You can start monit in verbose mode using the '-v' option.

It could help when you will send your monit log file (since monit start 
to the crash) + your monit control file, we can try to reproduce.

Also the monit coredump could help - you can analyze it using for 
example gdb:

  gdb <monit_binary> <core>

then run following commands in gdb prompt:

  info threads
  bt

Thanks,
Martin

Sean Porter wrote:
> First, thanks for monit.
>
> Unfortunately, I seem to be having some problems on OS X (10.3.9
> Server specifically).
>
> I can get a control file put together and validate that it was parsed
> correctly by connecting to the embedded webserver. However, when I try
> to run any of the commands, such as 'stop all', I get:
>
> # monit -c /path/to/my/controlfile stop all
> *** malloc[29425]: Deallocation of a pointer not malloced: 0x3006f4;
> This could be a double free(), or free() called with the middle of an
> allocated block; Try setting environment variable MallocHelp to see
> tools to help debug
>
> Others seem to have had this problem in the past:
>
> http://lists.nongnu.org/archive/html/monit-general/2003-07/msg00016.html
>
> but I didn't see any responses with resolution.
>
> Any ideas?
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general