HEADSUP: malloc changeover

Kris Kennaway kris at obsecurity.org
Fri Jan 13 12:18:31 PST 2006

On Fri, Jan 13, 2006 at 09:53:19PM +0200, Giorgos Keramidas wrote:
> On 2006-01-13 19:52, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
> >In message <1A89617A-5F0E-492E-8C21-10A4F679BCD2 at freebsd.org>, Jason Evans writes:
> >> The most likely types of application bugs that this malloc
> >> implementation will uncover are:
> >
> > And speaking from experience: You can do Jason a big favour by
> > trying your app with Electric Fence or similar before yelling
> > at him.
> HEH!  Definitely.  I have built & run at least four versions
> since January 11, two with DEBUG_FLAGS='-g' for both userland and
> kernel and two without.  As Jason said, we should probably keep
> looking for potential problems both in the new malloc() and the
> programs that use it, but the fact that my laptop still runs
> quite fine with several dozens of ports installed some time back
> in December seems to imply there aren't any _really_ _nasty_ bugs
> in malloc so far

There are several ports that have build failures due to application
bugs.  I think I emailed some of the maintainers already, but there
are more that are going to be (re-)exposed by some more recent changes
than that patchset I was testing.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060113/9c538660/attachment.bin

More information about the freebsd-current mailing list