On Thu, 18 May 2006, Jimmy Huang wrote:
> > If you want to fix mfprintf, man stdarg
> I was thinking about simply getting rid of it.  Have
> any idea why use mfprintf instead of regular fprintf?

It looks like it check if stdin is connected, and if not doesn't print
anything.  It's probably so the bot doesn't spew debugging stuff when it's run
by the daemon and no one is there to look at it.

It also flushes stdout, to avoid buffering.  That can be a problem if a
program writes to both stdout and stderr, sometimes the output isn't in proper
order do with stream buffering.

It is very strange that mfprintf would crash and not mprintf.  Do you have a
gdb backtrace of when it crashes?