All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV
Date: Sat, 21 Dec 2002 08:52:05 +0100	[thread overview]
Message-ID: <20021221075205.GZ31070@charite.de> (raw)
In-Reply-To: <20021221001334.GA7996@werewolf.able.es>

* J.A. Magallon <jamagallon@able.es>:

> For user space memory, there is no real OOM state. The system (glibc) just
> does not give you the memory, returns NULL in the malloc, and it is your
> responsibility to check malloc's return value. If you do not check it,
> you try to access a null pointer and _bang_. So in your case, after enough
> iterations on malloc() without free(), it returns NULL and you fall into
> a null pointer dereference.

Ergo: Squid is br0ken.

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   Ralf.Hildebrandt@charite.de
Charite Campus Mitte                            Tel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
Windows is the answer, but only if the question was 'what is the
intellectual equivalent of being a galley slave?' 


  reply	other threads:[~2002-12-21  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 11:48 2.4.20-aa and LARGE Squid process -> SIGSEGV Ralf Hildebrandt
2002-12-20 22:37 ` J.A. Magallon
2002-12-20 22:57   ` Ralf Hildebrandt
2002-12-21  0:13     ` J.A. Magallon
2002-12-21  7:52       ` Ralf Hildebrandt [this message]
2002-12-21  8:28         ` Reuben Farrelly
2002-12-21  9:06           ` Ralf Hildebrandt
2002-12-21  9:17             ` Reuben Farrelly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021221075205.GZ31070@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.