[PATCH] [BZ #10631] Clarify malloc error diagnostics to avoid confusion

[Marek Polacek]

On Wed, Sep 19, 2012 at 10:58:40AM -0400, Carlos O'Donell wrote:
> Does it actually matter what you or I *like*?
> 
> What do our users need to see?
> 
> > I'd be happy also with just:
> > *** in ./a.out: free(): invalid next size (fast): 0x084ed538 ***
> 
> That's just as terse as the original and doesn't help our users, it's not even clear
> that this an error :-(

You're right.

> What about this?
> ~~~
> *** Error `free(): invalid next size (fast)' in `./a.out' at 0x084ed538 ***
> ~~~

Yep, I really like this one ;)  But let's hear what others think.  Thanks,

	Marek