On 07 March 2007 15:07, Paulo J. Matos wrote: > Moreover, for some reason when using malloc, a lot of poisonous malloc > warning come up which are solved by using xmalloc instead, which is > another thing I cannot figure out. What is better in xmalloc than > malloc?
Take a look, the source for it is in libiberty. I think the only substantial difference is that if it runs out of memory it exits instead of returning a NULL pointer, meaning the rest of the code doesn't have to remember to check every single malloc return. cheers, DaveK -- Can't think of a witty .sigline today....