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. Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:50 UTC