Gentoo Archives: gentoo-user

From: Nikos Chantziaras <realnc@×××××.de>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: glibc memory corruption
Date: Thu, 08 Sep 2011 09:22:28
Message-Id: j4a1d0$4qe$1@dough.gmane.org
In Reply to: [gentoo-user] glibc memory corruption by Bill Kenworthy
1 On 09/08/2011 10:10 AM, Bill Kenworthy wrote:
2 > What would cause this?
3 >
4 > bunyip rpm # /opt/vmware/lib/vmware/bin/vmware
5 > *** glibc detected *** /opt/vmware/lib/vmware/bin/vmware: malloc():
6 > memory corruption: 0x09f35e80 ***
7 > ^C
8 > bunyip rpm #
9 >
10 > Ive tried doing a emerge -ep world
11 > glibc is
12 >
13 > * sys-libs/glibc
14 > Latest version available: 2.12.2
15 > Latest version installed: 2.12.2
16 > Size of downloaded files: 16,008 kB
17 > Homepage: http://www.gnu.org/software/libc/libc.html
18 > Description: GNU libc6 (also called glibc2) C library
19 > License: LGPL-2
20 >
21 > Ive tried vmware 7.1.3 and 7.1.4 from the vmware overlay and various
22 > kernels
23 >
24 > google has lots of occurrences but no fixes Ive found.
25 >
26 > Next step is to try a newer glibc but I would like to know if there are
27 > any more obvious steps to take first.
28
29 This isn't something you can fix. Only the VMware developers can do that.
30
31 Do you have the MALLOC_CHECK env var set, btw? AFAIK, these "glibc
32 detected" messages are the result of that. It's usually a bad idea as
33 it's slows down all software on your system.