Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
At Sun, 9 May 2004 19:39:59 +0200,
Vincent Lefevre wrote:
> > Second, I for one would consider the absence of overcommitment as a
> > bad misfeature. Good luck with the kernel bug report.
>
> The 2.6 kernel seems to have better memory handling (but I couldn't
> try yet). Concerning the 2.4 kernel, the problem seems to be the
> documentation.
2.4 is starting the handover process to 2.6 with its role of stable
version. So if you want to fix 2.4 kernel documents, please do.
I think we reached agreements that this bug is not glibc releated
problem. Thanks to Wolfram and Daniel. I would like to close this
bug. Vincent, ok?
Regards,
-- gotom
Reply to:
- References:
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Daniel Jacobowitz <dan@debian.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Vincent Lefevre <vincent@vinc17.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Daniel Jacobowitz <dan@debian.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Vincent Lefevre <vincent@vinc17.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Daniel Jacobowitz <dan@debian.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Wolfram Gloger <wg@malloc.de>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Vincent Lefevre <vincent@vinc17.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Vincent Lefevre <vincent@vinc17.org>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Wolfram Gloger <wg@malloc.de>
- Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
- From: Vincent Lefevre <vincent@vinc17.org>