This is the mail archive of the
mailing list for the glibc project.
Re: [email@example.com] libc/1447: malloc fails if the executable is called via /lib/ld-2.1.1.so ./testexec
- To: libc-alpha at sourceware dot cygnus dot com
- Subject: Re: [firstname.lastname@example.org] libc/1447: malloc fails if the executable is called via /lib/ld-2.1.1.so ./testexec
- From: Thorsten Kukuk <kukuk at suse dot de>
- Date: Sun, 14 Nov 1999 22:50:27 +0100
- References: <email@example.com>
On Sun, Nov 14, Andreas Jaeger wrote:
> 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
> I got:
> aj@arthur: 19:26:27 /tmp
> $ ./ld-malloc
> Malloc returned 8049790
> aj@arthur: 19:26:29 /tmp
> $ /lib/ld-linux.so.2 ./ld-malloc
> Malloc returned 80014198
> (compare the values - for Martin (?) Schwidefsky the second call
> failed completly - on my system (2.1.2 plus a number of patches) it's
> just a different value.
> Is this a bug in the current sources?
This sounds exactly like the problems we had with 2GB RAM machines.
Could it be that this people where malloc crashes or sunrpc due
building the glibc use kernels with 2GB RAM support enabled ?
(sunrpc crashes on malloc in the cases I know).
There was a bug in the kernel where the kernel rounds an address
wrong or so.
Thorsten Kukuk http://www.suse.de/~kukuk/ firstname.lastname@example.org
SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.