Alexander Pohoyda writes: > I'll try that tonight on the FreeBSD system. We have these options for > malloc: > > A All warnings (except for the warning about unknown flags being > set) become fatal. The process will call abort(3) in these > cases. > > J Each byte of new memory allocated by malloc(), realloc() or > reallocf() as well as all memory returned by free(), realloc() > or > reallocf() will be initialized to 0xd0. This options also sets > the ``R'' option. This is intended for debugging and will > impact > performance negatively. >
I assume what the original report was referring to: When memory is newly allocated (ie. just obtained from the memory bool by brk() or mmap()) it is zeroed (for security reasons). Some piece of the code seems to make the assumption implicitely that this is always the case - which is not as freed and reallocated memory that has not been give back to the system doesn't get zeroed. Depending wether the malloc in question happens during initialization (before any memory is freed) this can become a stability issue. It is sloppy programming anyway. Egbert. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
