This is the mail archive of the
mailing list for the glibc project.
Re: [firstname.lastname@example.org] libc/1447: malloc fails if the executable is called via /lib/ld-2.1.1.so ./testexec
- To: aj at suse dot de
- Subject: Re: [email@example.com] libc/1447: malloc fails if the executable is called via /lib/ld-2.1.1.so ./testexec
- From: Geoff Keating <geoffk at ozemail dot com dot au>
- Date: Mon, 15 Nov 1999 12:39:40 +1100
- CC: libc-alpha at sourceware dot cygnus dot com, schwidefsky at de dot ibm dot com
- References: <firstname.lastname@example.org>
> From: Andreas Jaeger <email@example.com>
> Date: 14 Nov 1999 19:29:46 +0100
> We received the appended bug report about a different behaviour of
> malloc when a program is called via /lib/ld-linux.so.2. On my systems
> Is this a bug in the current sources?
No. It's a bug in the kernel (all versions since at least 2.0). The
kernel decides to start mmap() right after the program's break.
It's dependent on the relative locations of ld.so and the executable.
It's the cause of a test failure on linux-ppc if you use recent
Geoffrey Keating <firstname.lastname@example.org>