Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV

[Reuben Farrelly]

[Forwarded for the purposes of continuity, Robert is not on lkml]

>Subject: Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV
>From: Robert Collins <[e-mail]>
>To: Reuben Farrelly <[e-mail]>
>Cc: Ralf Hildebrandt <[e-mail]>
>X-Mailer: Ximian Evolution 1.0.8
>Date: 21 Dec 2002 20:12:21 +1100
>
>On Sat, 2002-12-21 at 20:06, Ralf Hildebrandt wrote:
> > * Reuben Farrelly <[e-mail]>:
> >
> > > No, squid is not br0ken in this fashion.  If squid cannot be allocated
> > > enough memory by the system, it logs a message and _dies_.  Relevant 
> files
> > > to look at in your squid source are squid/lib/util.c for xcalloc() and
> > > xmalloc().
> >
> > Why can't squid allocate more than 1GB on a system with 2GB RAM?
>
>In general, it can.
>Folk run it with up to 2Gb with no special options on linux, all the
>time.
>
>Have you tried asking on the *right* list?
>Or running it under gdb?
>Or getting a stacktrace?
>
>SEGSIGV does *not* mean out of memory, you *may* have hit a genuine bug,
>but it *not* due to squid handling a failed malloc wrongly.
>
>Rob