This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Realloc returns NULL
- From: "Bruce Korb" <bkorb at gnu dot org>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: "Jeff Baumes" <jeff dot baumes at kitware dot com>, libc-help at sourceware dot org
- Date: Thu, 18 Dec 2008 16:59:26 -0800
- Subject: Re: Realloc returns NULL
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=nqRpI+c0N+sgeuVqLPTTPuIWQgULmsISezMRVZRN1p0=; b=WkhYd2MT7oRbjvFjik00DZrEws9VyeP2LMQvJKqDQyJDyagHBfC/bnjeVHrSDMkWY9 WsVFbx5CDFxcvffaKdtn6v+JJmhBj4sk/n2Yj8+kF4OpOkc45kXcjnVxeFxA8VYlClTr OpZzMyPAwB9HJiobFuiciwSyw726jjKPksUBg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=UvcB0a4jWVfG8ysWlhyfZRSuV/hIXtyXgGV+/Lh4c8YDoCh3CdzJAJHnx5r1AY2jHO dSxEOO+nRyA/zBq1vLoW0HkKO+mggOQ8lb0OjmXWpfnSlgwMlkhL6b6NpcyK2hp0MiEt wwQixsASMioB5SqPqztqV+T6PPP0ptNFF+Nrc=
- References: <2137e33e0812181411u7ce0e296rdf71d5af87fa191@mail.gmail.com> <119aab440812181418j5a8b3fd1qf3c8805898d3f367@mail.gmail.com> <2137e33e0812181535t4599a5dcg4b4f11fd32f738f9@mail.gmail.com> <119aab440812181553q4ac6a467q91b01b73e115b89f@mail.gmail.com>
Um, don't forget that the process itself may be limited.
On Thu, Dec 18, 2008 at 3:53 PM, Carlos O'Donell
<carlos@systemhalted.org> wrote:
> On Thu, Dec 18, 2008 at 6:35 PM, Jeff Baumes <jeff.baumes@kitware.com> wrote:
>> When I set MALLOC_CHECK_=3 in my environment to abort when a problem
>> is detected, I cannot get the program to crash. It apparently is using
>> a different version of realloc?
>
> No. The same version of realloc is used. At check action 3
> malloc_printerr will print error messages to stderr when it detects an
> error.
>
>> Any other ideas for tracking this down?
>
> Is your kernel mremap function broken?
>
> The glibc realloc will preferentially use the kernel to remap and
> expand the mmap'd chunk using mremap.
>
> Try a different, older or newer, kernel.
>
> Cheers,
> Carlos.
>