Re: "text 100,100 Cockatoo"

On Tue, 4 Oct 2011, [email protected] wrote:
>
> What have I run into?

I should mention that the most likely cause of this type of crash is 
heap corruption/misuse of some sort.  It is good to read the manual 
page for malloc() on your system to see what debugging aids can be 
enabled so that malloc can help detect errors.  For example, continued 
use of freed memory could cause this sort of problem.  Typically it is 
possible to tell BSD mallocs to not re-use any blocks and 
intentionally corrupt their content in a detectable fashion.  Also, 
guard pages can be added to detect writes outside of the allocated 
area.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1