NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/unix/aix/9366

Text File | 1992-09-03 | 1.6 KB | 39 lines

Newsgroups: comp.unix.aix
Path: sparky!uunet!panews!muddy.awdpa.ibm.com!steve
From: [e-mail] (Steve DeJarnett)
Subject: Re: Buggy malloc workaround
Message-ID: <[e-mail]>
Sender: [e-mail] (News Master)
Organization: IBM PS Programming, Palo Alto
References: <[e-mail]>
Date: Thu, 3 Sep 92 23:09:19 GMT
Lines: 27

In article <[e-mail]> [e-mail] (Murray S. Kucherawy [MFCF]) writes:
>My problems with putuserattr() calls are, according to IBM, caused by a bug
>in malloc implemented in AIX V3.2.  According to the man page for malloc,
>you can set the environment variable MALLOCTYPE to "3.1" and it will
>use the older version of malloc.
>
>It's not clear whether this is to be done at runtime or compile time.
>Anyone know? My program is to be run by a shell script remotely, and it will
>be tough to ensure that the environment variable is set.

    At runtime the code checks your MALLOCTYPE environment variable (if
you have one set).  Since you say you'll be running from a shell script, simply
insert a line before you call your program along the lines of:

    setenv MALLOCTYPE 3.1

(csh syntax, or: MALLOCTYPE=3.1; export MALLOCTYPE
    for bourne shell or korn shell)

That should ensure you get the 3.1 version of malloc when your program is run.

    Hope that helps...

Steve DeJarnett            Internet: [e-mail]
IBM PS Multimedia Palo Alto    UUCP:      uunet!ibmpa.awdpa.ibm.com!steve
[phone]            IBM VNET: dejarnet at austin (only if you must)
These opinions are my own.  I doubt IBM wants them.......