Messages in this thread |  | | | Date | Sat, 21 Dec 2002 08:52:05 +0100 | | From | Ralf Hildebrandt <> | | Subject | Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV |
| |
* 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?'
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |