Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uwm.edu!linac!unixhub!pfkeb From: pfkeb@ebnextk.SLAC.Stanford.EDU (Paul Kunz) Newsgroups: comp.sys.next Subject: Re: Library function redefinition Message-ID: Date: 3 Mar 91 04:11:59 GMT References: <1991Feb28.190319.22658@usenet.ins.cwru.edu> <1991Mar1.143756.12400@usenet.ins.cwru.edu> Sender: news@unixhub.SLAC.Stanford.EDU Organization: Stanford Linear Accelerator Center Lines: 25 Nntp-Posting-Host: ebnextk.slac.stanford.edu In-reply-to: scott@erick.gac.edu's message of 1 Mar 91 21:22:36 GMT In article scott@erick.gac.edu (Scott Hess) writes: Hmm. Something has just occurred to me - how in the world does the libMallocDebug.a library work? Presumably, the malloc and malloczone stuff is in the shared libraries, right? But, where is it in the MallocDebug library? Since it uses different calls, at the very least the routines are not the regular ones - whether they are shared or not makes no difference. So, apparently there's something that can be done to "fix" the multiply-defined thing, because otherwise we'd have multiple declaration problems with MallocDebug. Anybody know what that "fix" was? The answer was given at the last BaNG SIG meeting by Kevin who wrote the linker. If you want to redefine malloc() you can, BUT you must also redefine a suite of other closely related functions. To see that that list is, it is all the functions in libMallocDebug.a. I hope I got that right, if not, I'm sure someone will correct me. P.S. Earlier this week I posted that I ordered by upgrade boards in July and still not received them. This is my first post on my newly arrived upgrade board.