[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI __malloc_lock not GLOBAL on 2.6



Good news on this problem.  It seems that Purify also references __malloc_lock and fails under the beta version of Solaris 2.6.  This may mean that the final version of 2.6 libc.so will not hide the __malloc_lock variable.  If you are a Sun employee, I can send you the bugtraq number.

-greg

Gregory Burd - OpenStep Development Team, Sun Microsystems, Inc.


Begin forwarded message:

Sender: gburd@Eng
Date: Mon, 24 Feb 1997 08:50:34 -0800
From: Greg Burd <gburd@Eng>
Organization: Sun Microsystems, Inc.
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4u)
To: self-interest@self.smli.com
Subject: FYI __malloc_lock not GLOBAL on 2.6

I have been using Self on Solaris 2.5 for a while now.  I just tried it
on one of the 2.6 builds, and it fails with the following information.

toe [vm]% uname -a
SunOS toe 5.6 s297_26 sun4u sparc SUNW,Ultra-1
toe [vm]% ./Snapshot
ld.so.1: Self: fatal: relocation error: file Self: symbol __malloc_lock:
referenced symbol not found
Killed
toe [vm]%

It turns out that the __malloc_lock symbol is not global anymore.  So it
looks like the currently available Self binaries will not work on the
latest version of Solaris.  Is this fixable?

-greg

Gregory Burd - OpenStep Development Team, Sun Microsystems, Inc.