On 30 October 2011 19:25, Mihai Moldovan wrote: > As the first paste in http://trac.macports.org/ticket/27237#comment:14 > suggests (extracted from new_allocator.h:98), __p should be permitted to > be a null pointer.. which... well, is clearly not the case here for some > reason. Calling delete on a null pointer is permitted, but passing a null pointer to that allocator's deallocate function is not. Which is it?