To ease the management of which bugs needs to be fixed in which release
the use of target milestones have been enabled in bugzilla.
The current milestones are
2.5
3.0
3.1
This can be used in many ways.
a) When reading the bug reports it can easily be decided which Squid
version this need
On 17 Dec 2003 at 17:22, Henrik Nordstrom wrote:
> On Wed, 17 Dec 2003, Andres Kroonmaa wrote:
>
> > Yes, but there remains issue with memory fragmentation, to solve which
> > there is sense in coordinating assumptions of both malloc and pools.
> > Chunks are longlived objects, and they can ca
On Wed, 17 Dec 2003, Andres Kroonmaa wrote:
> Yes, but there remains issue with memory fragmentation, to solve which
> there is sense in coordinating assumptions of both malloc and pools.
> Chunks are longlived objects, and they can cause nasty holes in memspace,
> that can be relieved by use
On 17 Dec 2003, at 9:57, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> > But most interesting to me is in what ways has it bitten us?
>
> For a start there would need to be a official standard in how one is to
> replace the malloc implementation without risk for conflicts with the OS
> provided C/
On Wed, 17 Dec 2003, Andres Kroonmaa wrote:
> Could you list some requirements for malloc implementation that needs
> to be met to be considered optimal and safe malloc for Squid?
For a start there would need to be a official standard in how one is to
replace the malloc implementation without ris
Hello,
No comments on this one. Would someone please review proposed fix
if it is correct one for CVS?
Seems same bug as:
http://www.squid-cache.org/bugs/show_bug.cgi?id=637
--- Forwarded message follows ---
From: "Andres Kroonmaa" <[EMAIL PROTECTED]>
Organization: MicroL
On 15 Dec 2003, at 23:43, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> On Mon, 15 Dec 2003, Andres Kroonmaa wrote:
>
> > So far dlmalloc has been very good malloc. Why is it not safe anymore?
>
> It has never been really safe and this has bitten us to various degree
> several times in the past. T
