From owner-freebsd-questions Mon Jun 16 06:18:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04640 for questions-outgoing; Mon, 16 Jun 1997 06:18:07 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04629; Mon, 16 Jun 1997 06:17:57 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id IAA20146; Mon, 16 Jun 1997 08:17:40 -0500 (EST) Date: Mon, 16 Jun 1997 08:17:40 -0500 (EST) From: John Fieber To: Claudio Eichenberger cc: questions@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: xperfmon++ cannot perform realloc In-Reply-To: <199706160957.LAA08679@nty.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [This should have been directed to questions@freebsd.org.] On Mon, 16 Jun 1997, Claudio Eichenberger wrote: > I use FreeBSD 2.2.1 > > The tool xpermon++ does only run for a few seconds, i.e. it displays on > the screen but for just a few seconds. Then, apparantly it > tries to make a realloc which cannot be executed. > > alpha# xperfmon++ > Error: Cannot perform realloc > alpha# What version of XFree86 are you using? There is a known interaction between FreeBSD 2.2 (and later) and XFree86 3.3 that can generate this error. However, I vaguely recall getting this error from xperfmon++ with XFree86 3.2... ..anyway, the message comes from libXt and is caused by incorrect assumptions about what realloc() returns when given a size of zero. phk@freebsd.org can probably explain the details if you want them. The problem has been resolved in FreeBSD-current, but for 2.2.x, you have to re-build your libc with the src/lib/libc/stdlib/malloc.c from -current. A slightly easier stopgap measure is to link affected programs with the gnumalloc library (in /usr/lib/compat). -john